Docs » SignalFx µAPM concepts and terminology » MetricSets in SignalFx µAPM

MetricSets in SignalFx µAPM 🔗

Important

The original µAPM product, released in 2019, is now called µAPM Previous Generation (µAPM PG). In the documentation, µAPM now refers to the product released on March 31, 2020.

If you are using µAPM Previous Generation (µAPM PG), see µAPM PG Traces, Spans, Metrics, and Metadata.

MetricSets are categories of metrics about traces and spans you can use for real-time monitoring and high-cardinality troubleshooting. MetricSets are specific to µAPM, but are similar to metrics and metric time-series for infrastructure monitoring that SignalFx uses to populate charts and generate alerts. There are two categories of MetricSets: Monitoring and Troubleshooting.

Monitoring MetricSets are for real-time monitoring and alerting.

Troubleshooting MetricSets are for filtering service maps and breaking down SLIs to enable historical comparison for spans and workflows.

Every identity has Troubleshooting MetricSets, but not every identity has Monitoring MetricSets.

Troubleshooting MetricSets are stored for eight days by default, along with traces. Each Troubleshooting MetricSet has the following metrics available to use for troubleshooting:

  • Request rate
  • Error rate
  • Root cause error rate
  • Latency: min, max, P50, P90, P99

Monitoring MetricSets are stored for thirteen months by default. Each Monitoring MetricSet has the following metrics available for monitoring and alerting:

  • Request rate
  • Error rate
  • Latency: min, max, P50, P90, P99

Default identities and MetricSets 🔗

By default, µAPM creates the following identities and associated MetricSets.

The resulting total number of Troubleshooting MetricSets is the sum of all identities. The resulting total number of Monitoring MetricSets is the sum of Service, Endpoint, and Workflow identities. For more information about identities, see Identities in SignalFx µAPM.

APM object Description Identity example Troubleshooting MetricSet Monitoring MetricSet
Service Identities for all services Service‑1 Yes Yes
Endpoint Identities for all endpoints

Service‑1.Endpoint‑1.HTTPMethod

(or Service‑1.InitEndpoint‑1 if HTTPMethod is absent)

Yes Yes
Workflow Identities for all initiating endpoints

Service‑1.InitEndpoint‑1.HTTPMethod

(or Service‑1.InitEndpoint‑1 if HTTPMethod is absent)

Yes Yes
Edge Identities for all edges between services Service‑1.Endpoint‑1.HTTPMethod‑>Service‑2.Endpoint‑2.HTTPMethod Yes No
Operation Identities for all spans within services Service‑1.Operation‑1 No No