<STACKSTATE_RECEIVER_API_KEY>
is set during StackState installation.<STACKSTATE_RECEIVER_API_ADDRESS>
is specific to your installation of StackState.<STACKSTATE_RECEIVER_API_KEY>
is set during StackState installation.<STACKSTATE_RECEIVER_API_ADDRESS>
is specific to your installation of StackState. For details see StackState Receiver API.docker-compose.yml
with the following content. Update to include details of your StackState instance:<STACKSTATE_RECEIVER_API_KEY>
is set during StackState installation.<STACKSTATE_RECEIVER_API_ADDRESS>
is specific to your installation of StackState. For details see StackState Receiver API.<CLUSTER_NAME>
is the name you would like to give this cluster/etc/stackstate-agent/stackstate.yaml
. The configuration file contains the STS_API_KEY
and STS_STS_URL
environment variables set when the Docker command is run. No further configuration should be required, however, a number of advanced configuration options are available./etc/stackstate-agent/conf.d/
when the container is started.CURL_CA_BUNDLE
environment variable:/var/log/stackstate-agent/agent.log
/var/log/stackstate-agent/process-agent.log
INFO
. To assist in troubleshooting, the Agent log level can be set to DEBUG
. This will enable verbose logging and all errors encountered will be reported in the Agent log files.DEBUG
for an Agent running on Docker, use the STS_LOG_LEVEL
environment variable. Other optional logging settings:STS_LOG_PAYLOADS: "true"
- include the topology/telemetry payloads sent to StackState in the Agent log.STS_LOG_TO_CONSOLE: "true"
- write log output to the container stdout.