5장. Configuring action log storage for Elasticsearch and Splunk

Procedure

1. Obtain an Elasticsearch account.

2. Update your Red Hat Quay config.yaml file to include the following information:

   # ...
   LOGS_MODEL: elasticsearch 

   1

   
   LOGS_MODEL_CONFIG:
       producer: elasticsearch 

   2

   
       elasticsearch_config:
           host: http://<host.elasticsearch.example>:<port> 

   3

   
           port: 9200 

   4

   
           access_key: <access_key> 

   5

   
           secret_key: <secret_key> 

   6

   
           use_ssl: True 

   7

   
           index_prefix: <logentry> 

   8

   
           aws_region: <us-east-1> 

   9

   
   # ...

   1

   The method for handling log data.

   2

   Choose either Elasticsearch or Kinesis to direct logs to an intermediate Kinesis stream on AWS. You need to set up your own pipeline to send logs from Kinesis to Elasticsearch, for example, Logstash.

   3

   The hostname or IP address of the system providing the Elasticsearch service.

   4

   The port number providing the Elasticsearch service on the host you just entered. Note that the port must be accessible from all systems running the Red Hat Quay registry. The default is TCP port 9200.

   5

   The access key needed to gain access to the Elasticsearch service, if required.

   6

   The secret key needed to gain access to the Elasticsearch service, if required.

   7

   Whether to use SSL/TLS for Elasticsearch. Defaults to True.

   8

   Choose a prefix to attach to log entries.

   9

   If you are running on AWS, set the AWS region (otherwise, leave it blank).

3. Optional. If you are using Kinesis as your logs producer, you must include the following fields in your config.yaml file:

       kinesis_stream_config:
           stream_name: <kinesis_stream_name> 

   1

   
           access_key: <aws_access_key> 

   2

   
           secret_key: <aws_secret_key> 

   3

   
           aws_region: <aws_region> 

   4

   1

   The name of the Kinesis stream.

   2

   The name of the AWS access key needed to gain access to the Kinesis stream, if required.

   3

   The name of the AWS secret key needed to gain access to the Kinesis stream, if required.

   4

   The Amazon Web Services (AWS) region.

4. Save your config.yaml file and restart your Red Hat Quay deployment.