After the problem has been defined and its risk and impact assessed, collect data for analysis. You can use the following steps to collect data, depending on the nature of the problem.
Before you begin
You must be signed in to the Grid Manager using a supported browser.
You must have specific access permissions.
More information
Performing ingest and retrieval tests
To troubleshoot ingest and retrieval performance issues, you can perform a simple test that uses a workstation in the place of the actual client application and analyze the store/retrieve performance during the test compared to the performance normally seen with the client application.
Listing recent changes
It is important that you make a list of any recent changes made to the StorageGRID system or its environment.
Checking connectivity status
Confirm that servers are online and connected to each other. In the Grid Topology tree, look for grid nodes whose state is unknown (blue) or are administratively down, that is, that have been purposely stopped (gray).
Reviewing alarms
An alarm is triggered when the value of an attribute reaches a set alarm threshold value. Node icons that are not green indicate that an alarm has been triggered.
Plotting trends
Reports (both chart and text) are an invaluable tool when troubleshooting. The fastest way to create a chart is to click the Chart button on the Overview tab of a component or service. This is known as an immediate report. You can also create charts from the Reports tab.
Establishing baselines
Baseline information is operational data during normal system operations that provides clues that can help you solve problems.
Monitoring events
You can monitor any events that are detected by a grid node to help with troubleshooting. The Last Event provides an area of focus when an error occurs.
Collecting log files and system data
To help troubleshoot a problem, you can retrieve log files and system data (including configuration data) for your StorageGRID system. This information is retrieved using the Grid Manager.
Reviewing audit messages
Audit messages can help you get a better understanding of the detailed operations of your StorageGRID system. You can use audit logs to troubleshoot issues and to evaluate performance.
Triggering an AutoSupport message
To assist technical support in troubleshooting problems with the StorageGRID system, you can manually trigger the sending of an AutoSupport message to technical support.
Reviewing support metrics
When troubleshooting an issue, you can work with technical support to review detailed metrics and charts for your StorageGRID system.
Running foreground verification
Foreground verification enables you to verify the existence of data on a Storage Node. Missing object data might indicate that an issue exists with the underlying storage device.
Confirming object data locations
Depending on the problem, you might want to confirm where object data is being stored. For example, you might want to verify that the ILM policy is performing as expected and object data is being stored where intended.