8.4.2. User events
User events track activity across Red Hat Quay, such as repository pushes, tag creations, deletions, and permission changes. These events are recorded in Redis as part of the activity stream and can be accessed through the API or web interface.
The following user event fields are available for Redis deployments.
| Field | Type | Description |
|---|---|---|
|
USER_EVENTS_REDIS | Object | Redis connection details for user event handling. |
|
.host | String |
The hostname at which Redis is accessible. |
|
.port | Number |
The port at which Redis is accessible. |
| .password | String |
The password to connect to the Redis instance. |
| .ssl | Boolean | Whether to enable TLS communication between Redis and Quay. Defaults to false. |
|
.ssl_keyfile | String |
The name of the key database file, which houses the client certificate to be used. |
|
.ssl_certfile | String |
Used for specifying the file path of the SSL certificate. |
|
.ssl_cert_reqs | String |
Used to specify the level of certificate validation to be performed during the SSL/TLS handshake. |
|
.ssl_ca_certs | String |
Used to specify the path to a file containing a list of trusted Certificate Authority (CA) certificates. |
|
.ssl_ca_data | String |
Used to specify a string containing the trusted CA certificates in PEM format. |
|
.ssl_check_hostname | Boolean |
Used when setting up an SSL/TLS connection to a server. It specifies whether the client should check that the hostname in the server’s SSL/TLS certificate matches the hostname of the server it is connecting to. |
Redis user events example
# ...
USER_EVENTS_REDIS:
host: <quay-redis.example.com>
port: 6379
password: <example_password>
ssl: true
ssl_keyfile: /etc/ssl/private/redis-client.key
ssl_certfile: /etc/ssl/certs/redis-client.crt
ssl_cert_reqs: <required_certificate>
ssl_ca_certs: /etc/ssl/certs/ca-bundle.crt
ssl_check_hostname: true
# ...