Configure traces
This page describes StackState version 4.2.
The StackState 4.2 version range is End of Life (EOL) and no longer supported. We encourage customers still running the 4.2 version range to upgrade to a more recent release.
Traces can be viewed in the Traces Perspective screen in the StackState UI. To enable tracing, you first need to install the StackState Agent StackPack and configure one or more tracing integrations, see how to set up traces. This page describes how to override the default tracing configuration and hide traces from the StackState UI.
Note that it is not advised to change the default configuration for tracing.
Retention limits
It is not advised to change the default settings for retention!
Retention limits specify the index size of StackState and how long data is stored. Changing the default value here can lead to reduced stability and may cause trace and topology data to go out of sync.
If required, overrides to the default retention limits can be placed in the file etc/kafka-to-es/application.conf
:
Restart the component for changes to take affect.
For more details, see how to configure the StackState metrics, events and traces data store.
Rate limits
It is not advised to change the default settings for rate limits!
If required, overrides to the default rate limits can be placed in the file etc/stackstate-receiver/application.conf
:
Restart the component for changes to take affect.
Turn off tracing
Tracing cannot be turned off in StackState. If required, you can hide traces from the StackState UI in the file etc/application_stackstate.conf
by setting:
Restart the component for changes to take affect.
Last updated