Skip to main content
A newer release of this product is available.

Monitor and audit operations

Contributors netapp-perveilerk netapp-lhalbert netapp-madkat ssantho3

You can monitor workloads and efficiencies for client operations by viewing transaction trends for the entire grid, or for specific nodes. You can use audit messages to monitor client operations and transactions.

Monitor object ingest and retrieval rates

You can monitor object ingest and retrieval rates as well as metrics for object counts, queries, and verification. You can view the number of successful and failed attempts by client applications to read, write, and modify objects in the StorageGRID system.

Steps
  1. Sign in to the Grid Manager using a supported web browser.

  2. On the dashboard, select Performance > S3 operations or Performance > Swift operations.

    This section summarizes the number of client operations performed by your StorageGRID system. Protocol rates are averaged over the last two minutes.

  3. Select NODES.

  4. From the Nodes home page (deployment level), click the Load Balancer tab.

    The charts show trends for all client traffic directed to load balancer endpoints within the grid. You can select a time interval in hours, days, weeks, months, or years, or you can apply a custom interval.

  5. From the Nodes home page (deployment level), click the Objects tab.

    The chart shows ingest and retrieve rates for your entire StorageGRID system in bytes per second and total bytes. You can select a time interval in hours, days, weeks, months, or years, or you can apply a custom interval.

  6. To see information for a particular Storage Node, select the node from the list on the left, and click the Objects tab.

    The chart shows the object ingest and retrieval rates for this Storage Node. The tab also includes metrics for object counts, queries, and verification. You can click the labels to see the definitions of these metrics.

    screenshot of Nodes > _Storage Node_ > Objects > attribute help
  7. If you want even more detail:

    1. Select SUPPORT > Tools > Grid topology.

    2. Select site > Overview > Main.

      The API Operations section displays summary information for the entire grid.

    3. Select Storage Node > LDR > client application > Overview > Main

      The Operations section displays summary information for the selected Storage Node.

Access and review audit logs

Audit messages are generated by StorageGRID services and stored in text log files. API-specific audit messages in the audit logs provide critical security, operation, and performance monitoring data that can help you evaluate the health of your system.

Before you begin
  • You must have specific access permissions.

  • You must have the Passwords.txt file.

  • You must know the IP address of an Admin Node.

About this task

The active audit log file is named audit.log, and it is stored on Admin Nodes.

Once a day, the active audit.log file is saved, and a new audit.log file is started. The name of the saved file indicates when it was saved, in the format yyyy-mm-dd.txt.

After a day, the saved file is compressed and renamed, in the format yyyy-mm-dd.txt.gz, which preserves the original date.

This example shows the active audit.log file, the previous day's file (2018-04-15.txt), and the compressed file for the prior day (2018-04-14.txt.gz).

audit.log
2018-04-15.txt
2018-04-14.txt.gz
Steps
  1. Log in to an Admin Node:

    1. Enter the following command: ssh admin@primary_Admin_Node_IP

    2. Enter the password listed in the Passwords.txt file.

    3. Enter the following command to switch to root: su -

    4. Enter the password listed in the Passwords.txt file.

      When you are logged in as root, the prompt changes from $ to #.

  2. Go to the directory containing the audit log files:cd /var/local/audit/export

  3. View the current or a saved audit log file, as required.

Swift operations tracked in the audit logs

All successful storage DELETE, GET, HEAD, POST, and PUT operations are tracked in the StorageGRID audit log. Failures aren't logged, nor are info, auth, or OPTIONS requests.

Information is tracked for the following Swift operations.

Account operations