Troubleshooting Self-Hosted Classic Edition (Docker)
You can run the instana debug command to dump the debug information of the system where the backend is running. In case something is wrong, this is a first step.
The debugging information includes information about the system, the hardware, the state of all the installed components, and their health. This data is collected locally, and nothing is transmitted over the wire.
A temporary directory (instana-debug_{timestamp}
) is created in the same directory as where you run the instana debug
command with information about the system, the hardware, the state of all the installed components
and their health, and component configuration settings, which give support engineers helpful information. Additionally, all information is written into instana-debug_{timestamp}.tar.gz
file alongside.
Adjusting log level for Instana services
You can adjust the log level to DEBUG
for a specific service for 15 minutes.
-
Get the Instana Docker container names by running the following command:
docker ps --format '{{ .Names }}' | cut -d'-' -f 2-5
-
Set the log level to
DEBUG
for a specific Instana service by running the following command:instana configure debug-log {service}
Replace {service} with the Intana Docker container name related to the service that you want to debug.
For example, run the following command to set the log level to
DEBUG
for the Instana containerinstana-acceptor
.instana configure debug-log acceptor
Some metrics are not displayed on dashboards
If some metrics are not displayed on dashboards, it's possible that the limit for metrics is reached. The metric limit is set to 3000, by default. To increase the limit for metrics, update the settings.hcl
file as shown in the following
example:
toggle "config.max.metrics" {
value = "6000"
}
Then, run the instana update
command, to apply the changes.