Use and manage Troubleshooting MetricSets
Learn how to use TMS to filter and break down metrics, as well as review or modify existing TMS.
Use this topic to learn how to use and manage Troubleshooting MetricSets (TMS).
Use Troubleshooting MetricSets to filter and break down metrics
Every TMS creates the following metrics, also known as Request, Error, and Duration (RED) metrics. The following metrics appear when you select a service from the service map in the Troubleshooting view:
Request rate
Error rate
Root cause error rate
p50, p90, and p99 latency
The measurement precision of Troubleshooting MetricSets is 10 seconds. Splunk APM reports quantiles from a distribution of metrics for each 10-second reporting window.
TMS appear on the service map and in Tag Spotlight. Use TMS to filter the service map and create breakdowns across the values of a given indexed span tag or process.
See Scenario: Kai investigates the root cause of an error with the Splunk APM service map to learn more about using RED metrics in the service map.
See Scenario: Deepu finds the root cause of an error using Tag Spotlight to learn how indexed tags are used in troubleshooting.
Manage Troubleshooting MetricSets
After you've successfully indexed a span tag or process, Splunk APM saves the configuration in the APM MetricSets page in Data Configuration. Go to this page to view the index scope and status of the span tag or process.
You can modify the configuration for existing indexed tags and processes, including adding and removing services for specific indexed tags or processes and modifying the scope. You can also pause or stop indexing without deleting the configuration. This is useful when you want to temporarily stop indexing a span tag or process, but don't want to remove the configuration.
To review or modify existing indexed span tags or processes, do the following:
Go to Settings then Data Configuration then APM MetricSets.
Find the indexed span tag or process you want to view under the Custom MetricSets section of the configuration table.
See Status of configured Troubleshooting MetricSets to interpret the status of each indexed span tag or process.
Make any desired changes using the buttons in the Actions column:
Use the pencil button to edit the scope of an indexed span tag or process.
Use the pause button to pause generating MetricSets for a given span tag or process.
Use the trash button to delete a MetricSet configuration.
About Troubleshooting MetricSets statuses
After you've configured custom Troubleshooting MetricSets, you can see their status. The following table lists all available statuses:
|
Status |
Description |
|---|---|
|
Active |
The application is indexing the span tag or process to create Troubleshooting MetricSets. |
|
Paused |
You or another administrator paused indexing for the span tag or process. The application isn't generating Troubleshooting MetricSets for the span tag or process, and you can't view any data you previously indexed for it. |
|
Stopped |
The application stopped indexing the span tag or process and is no longer generating Troubleshooting MetricSets for the span tag or process. You can't view any data you previously indexed. |
Manage Database MetricSets
You can pause and resume indexing Database Query Performance data from the Standard MetricSets section of APM MetricSets. You can also control the indexing of SQL and NoSQL tags separately.
To pause the indexing of Database Query Performance data, select Pause indexing next to the database type. To resume, select Resume indexing.