Skip to main content
How to enable StorageGRID in your environment

StorageGRID log analytics using ELK stack

Contributors netapp-aronk

With the StorageGRID 11.6 syslog forward feature, you can configure an external syslog server to collect and analyze StorageGRID log messages. ELK (Elasticsearch, Logstash, Kibana) has become one of the most popular log analytics solutions. Watch the StorageGRID log analysis using ELK video to view a sample ELK configuration and how it can be used to identify and troubleshoot failed S3 requests.
This article provides sample files of Logstash configuration, Kibana queries, charts and dashboard to give you a quick start for StorageGRID log management and analytics.


  • StorageGRID or higher

  • ELK (Elasticsearch, Logstash and Kibana) 7.1x or higher installed and in operation

Sample files


Readers are familiar with StorageGRID and ELK terminology and operations.


Two sample versions are provided due to differences in names defined by grok patterns.
For example, the SYSLOGBASE grok pattern in Logstash config file defines field names differently depending on the installed Logstash version.

match => {"message" => '<%{POSINT:syslog_pri}>%{SYSLOGBASE} %{GREEDYDATA:msg-details}'}

Logstash 7.17 sample

Logstash 7.17 sample

Logstash 8.23 sample

Logstash 8.23 sample


  1. Unzip the provided sample based on your installed ELK version.
    The sample folder includes two Logstash config samples:
    sglog-2-file.conf: this config file outputs StorageGRID log messages to a file on Logstash without data transformation. You can use this to confirm Logstash is receiveing StorageGRID messages or to help understand StorageGRID log patterns.
    sglog-2-es.conf: this config file transforms StorageGRID log messages using various pattern and filters. It includes example drop statements, which drop messages based on patterns or filter. The output is sent to Elasticsearch for indexing.
    Customize the selected config file according to the instruction inside the file.

  2. Test the customized config file:

    /usr/share/logstash/bin/logstash --config.test_and_exit -f <config-file-path/file>

    If the last line returned is similar to the below line, the config file has no syntax errors:

    [LogStash::Runner] runner - Using config.test_and_exit mode. Config Validation Result: OK. Exiting Logstash
  3. Copy the customized conf file to the Logstash server's config: /etc/logstash/conf.d
    If you have not enabled config.reload.automatic in /etc/logstash/logstash.yml, restart the Logstash service. Otherwise, wait for the config reload interval to elapse.

     grep reload /etc/logstash/logstash.yml
    # Periodically check if the configuration has changed and reload the pipeline
    config.reload.automatic: true
    config.reload.interval: 5s
  4. Check /var/log/logstash/logstash-plain.log and confirm there are no errors starting Logstash with the new config file.

  5. Confirm TCP port is started and listening.
    In this example, TCP port 5000 is used.

    netstat -ntpa | grep 5000
    tcp6       0      0 :::5000                 :::*                    LISTEN      25744/java
  6. From the StorageGRID manager GUI, configure external syslog server to send log messages to Logstash. Refer to the demo video for details.

  7. You need to configure or disable firewall on the Logstash server to allow StorageGRID nodes connection to the defined TCP port.

  8. From Kibana GUI, select Management → Dev Tools. On the Console page, run this GET command to confirm new indices are created on Elasticsearch.

    GET /_cat/indices/*?v=true&s=index
  9. From Kibana GUI, create index pattern (ELK 7.x) or data view (ELK 8.x).

  10. From Kibana GUI, enter 'saved objects' in the search box which is located in the top center.
    On the Saved Objects page, select Import. Under Import options, select 'Request action on conflict'

    Kibana Import options

    Import elk<version>-query-chart-sample.ndjson.
    When prompted to resolve the conflict, select the index pattern or data view you created in step 8.

    Kibana Conflict

    The following Kibana objects are imported:
    * audit-msg-s3rq-orlm
    * bycast log s3 related messages
    * loglevel warning or above
    * failed security event
    * s3 requests count based on bycast.log
    * HTTP status code
    * audit msg breakdown by type
    * average s3 response time
    * S3 request dashboard using the above charts.

You are now ready to perform StorageGRID log analysis using Kibana.