diff --git a/signalfx-org-metrics/metrics.yaml b/signalfx-org-metrics/metrics.yaml index c6a6e0d1..638b5a8e 100644 --- a/signalfx-org-metrics/metrics.yaml +++ b/signalfx-org-metrics/metrics.yaml @@ -1,6 +1,5 @@ sf.org.apm.grossContentBytesReceived: - brief: The volume of bytes Splunk APM receives off the wire before filtering - and throttling. + brief: The volume of bytes Splunk APM receives off the wire before discarding invalid and throttled spans. description: | The volume of bytes Splunk APM receives off the wire before filtering and throttling. This content could be compressed. @@ -12,10 +11,10 @@ sf.org.apm.grossContentBytesReceived: sf.org.apm.grossSpanBytesReceived: brief: The number of bytes Splunk APM receives from spans after decompression - but before filtering and throttling. + but before discarding invalid and throttled spans. description: | The number of bytes Splunk APM receives from spans after - decompression but before filtering and throttling. + decompression but before discarding invalid and throttled spans. * Dimension(s): `orgId` * Data resolution: 1 second @@ -24,11 +23,10 @@ sf.org.apm.grossSpanBytesReceived: sf.org.apm.grossSpanBytesReceivedByToken: brief: The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and - throttling. + from ingested span data after decompression but before discarding invalid and throttled spans. description: | The number of bytes Splunk APM receives for a specific access token - from ingested span data after decompression but before filtering and throttling. + from ingested span data after decompression but before discarding invalid and throttled spans. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -36,9 +34,9 @@ sf.org.apm.grossSpanBytesReceivedByToken: title: sf.org.apm.grossSpanBytesReceivedByToken sf.org.apm.grossSpansReceived: - brief: The number of spans Splunk APM received before filtering and throttling. + brief: The number of spans Splunk APM received before discarding invalid and throttled spans. description: | - The number of spans Splunk APM received before filtering or throttling. + The number of spans Splunk APM received before discarding invalid and throttled spans. * Dimension(s): `orgId` * Data resolution: 1 second @@ -108,10 +106,10 @@ sf.org.apm.numHosts: sf.org.apm.numSpanBytesReceived: brief: The number of bytes Splunk APM accepts from ingested span data - after decompression after filtering and throttling. + after decompression and discarding invalid and throttled spans. description: | The number of bytes Splunk APM accepts from ingested span - data after decompression after filtering and throttling. + data after decompression and discarding invalid and throttled spans. * Dimension(s): `orgId` * Data resolution: 1 second @@ -120,22 +118,57 @@ sf.org.apm.numSpanBytesReceived: sf.org.apm.numSpanBytesReceivedByToken: brief: The number of bytes Splunk APM accepts for a specific access token - for a span after decompression after filtering and throttling. + for a span after decompression and discarding invalid and throttled spans. description: | The number of bytes Splunk APM accepts for a specific access token - for a span after decompression after filtering and throttling. + for a span after decompression and discarding invalid and throttled spans. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second metric_type: counter title: sf.org.apm.numSpanBytesReceivedByToken +sf.org.apm.numSpansDroppedBlocked: + brief: The number of spans that APM was unable to process or has dropped due to a blocked trace or too many spans in the trace. + description: | + The number of spans that APM was unable to process or has dropped. A span can be dropped for the following reasons: + * blockedTraceID: If any ingest endpoint reaches the 100k limit for spans in a given trace, then the trace is added to the list of blocked traces so that all the ingest endpoints block any future spans. + * tooManySpansInTrace: Trace submitted over 100k spans at the first ingest stage + + ``sf.org.apm.numSpansDroppedBlocked`` has the following dimensions and data resolution: + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.numSpansDroppedBlocked + +sf.org.apm.numSpansDroppedBlockedByToken: + brief: The number of spans for a specific token that APM was unable to process or has dropped due to a blocked trace or too many spans in the trace + description: | + The number of spans for a specific token that APM was unable to process or has dropped. A span can be + dropped for the following reasons: + * blockedTraceID: If any ingest endpoint reaches the 100k limit for spans in a given trace, then the trace is added to the list of blocked traces so that all the ingest endpoints block any future spans. + * tooManySpansInTrace: Trace submitted over 100k spans at the first ingest stage + + ``sf.org.apm.numSpansDroppedBlocked`` has the following dimensions and data resolution: + + * Dimension(s): `orgId` + * Data resolution: 1 second + metric_type: counter + title: sf.org.apm.numSpansDroppedBlockedByToken + sf.org.apm.numSpansDroppedInvalid: brief: The number of invalid spans Splunk APM receives. description: | The number of invalid spans Splunk APM receives. A span can be - invalid if there is no start time, trace ID, or service associated with it, - or if there are too many spans in the trace. + invalid for the following reasons: + * invalidTraceID: Trace ID isn't a 16-byte or 32-byte hex number + * noOperationName: No operation name was provided + * spanTooLarge: Span body exceeds 64KiB + * zeroStartTime: The start timestamp is 0 + * zipkinV2BinaryAnnotations: Unsupported Zipkin feature + + ``sf.org.apm.numSpansDroppedInvalid`` has the following dimensions and data resolution: * Dimension(s): `orgId` * Data resolution: 1 second @@ -147,8 +180,14 @@ sf.org.apm.numSpansDroppedInvalidByToken: token. description: | The number of invalid spans Splunk APM receives for a specific - access token. A span can be invalid if there is no start time, trace ID, or - service associated with it, or if there are too many spans in the trace. + access token. A span can be invalid for the following reasons: + * invalidTraceID: Trace ID isn't a 16-byte or 32-byte hex number + * noOperationName: No operation name was provided + * spanTooLarge: Span body exceeds 64KiB + * zeroStartTime: The start timestamp is 0 + * zipkinV2BinaryAnnotations: Unsupported Zipkin feature + + ``sf.org.apm.numSpansDroppedInvalidByToken`` has the following dimensions and data resolution: * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -202,9 +241,9 @@ sf.org.apm.numSpansDroppedThrottleByToken: title: sf.org.apm.numSpansDroppedThrottleByToken sf.org.apm.numSpansReceived: - brief: The number of spans Splunk APM accepts after filtering and throttling. + brief: The number of spans Splunk APM accepts after discarding invalid and throttled spans. description: | - The number of spans Splunk APM accepts after filtering and throttling. + The number of spans Splunk APM accepts after discarding invalid and throttled spans. * Dimension(s): `orgId` * Data resolution: 1 second @@ -213,10 +252,10 @@ sf.org.apm.numSpansReceived: sf.org.apm.numSpansReceivedByToken: brief: The number of spans Splunk APM received for a specific access token - after filtering and throttling. + after discarding invalid and throttled spans. description: | The number of spans Splunk APM received for a specific access token - after filtering and throttling. + after discarding invalid and throttled spans. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -225,10 +264,10 @@ sf.org.apm.numSpansReceivedByToken: sf.org.apm.grossSpansReceivedByToken: brief: The number of spans Splunk APM receives for a specific access token - before filtering and throttling. + before discarding invalid and throttled spans. description: | The number of spans Splunk APM receives for a specific access token - before filtering or throttling. + before discarding invalid and throttled spans. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -326,11 +365,9 @@ sf.org.apm.numTroubleshootingMetricSets: title: sf.org.apm.numTroubleshootingMetricSets sf.org.apm.numContentBytesReceived: - brief: The volume of bytes Splunk APM accepts off the wire after filtering - and throttling. + brief: The volume of bytes Splunk APM accepts off the wire after discarding invalid and throttled spans. description: | - The volume of bytes Splunk APM accepts off the wire after filtering - and throttling. This content could be compressed. + The volume of bytes Splunk APM accepts off the wire discarding invalid and throttled spans. This content could be compressed. * Dimension(s): `orgId` * Data resolution: 1 second @@ -339,10 +376,10 @@ sf.org.apm.numContentBytesReceived: sf.org.apm.grossContentBytesReceivedByToken: brief: The volume of bytes Splunk APM receives off the wire for a specific access - token before filtering and throttling. + token before discarding invalid and throttled spans. description: | The volume of bytes Splunk APM receives off the wire for a specific - access token before filtering and throttling. This content could be compressed. + access token before discarding invalid and throttled spans. This content could be compressed. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -351,10 +388,10 @@ sf.org.apm.grossContentBytesReceivedByToken: sf.org.apm.numContentBytesReceivedByToken: brief: The volume of bytes Splunk APM accepts off the wire for a specific access - token after filtering and throttling. + token after discarding invalid and throttled spans. description: | The volume of bytes Splunk APM accepts off the wire for a specific - access token after filtering and throttling. This content could be compressed. + access token after discarding invalid and throttled spans. This content could be compressed. * Dimension(s): `orgId`, `tokenId` * Data resolution: 1 second @@ -368,6 +405,16 @@ sf.org.abortedDetectors: or data points, whichever caused the detector to stop metric_type: cumulative title: sf.org.abortedDetectors + +sf.org.cloud.grossDpmContentBytesReceived: + brief: Number of content bytes received, but not necessarily admitted, for Cloud services + description: | + Number of content bytes received, but not necessarily admitted, for Cloud services + + * Dimension(s): `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.cloud.grossDpmContentBytesReceived sf.org.datapointsTotalCountByToken: brief: Total datapoints by token @@ -930,8 +977,8 @@ sf.org.num.migrationmarker: title: sf.org.num.migrationmarker sf.org.num.mutingactive: - brief: Number of active muting rules NBED - description: Number of active muting rules NBED. + brief: Number of active muting rules + description: Number of active muting rules metric_type: gauge title: sf.org.num.mutingactive @@ -1128,9 +1175,9 @@ sf.org.numApmApiCalls: title: sf.org.numApmApiCalls sf.org.numApmBundledMetrics: - brief: APM Bundled Metrics limit for your org + brief: Number of APM Bundled Metrics for your org description: | - APM Bundled Metrics limit for your org. + Number of APM Bundled Metrics for your org. * Dimension(s): `orgId` * Data resolution: 10 minutes @@ -1138,9 +1185,9 @@ sf.org.numApmBundledMetrics: title: sf.org.numApmBundledMetrics sf.org.numApmBundledMetricsByToken: - brief: APM Bundled Metrics limit for your org, for a token + brief: Number of APM Bundled Metrics for your org, for a token description: | - APM Bundled Metrics limit for your org for a specific token. + Number of APM Bundled Metrics for your org for a specific token. * Dimension(s): `orgId`, `tokenId` * Data resolution: 10 minutes @@ -1325,6 +1372,7 @@ sf.org.numDatapointsDroppedBatchSizeByToken: brief: Number of data points dropped because a single request contained more than 100,000 data points, by token. description: | Number of data points dropped because a single request contained more than 100,000 data points, per token. In this scenario, Observability Cloud drops data points because it perceives sending more than 100,000 data points in a single request as excessive. + * Dimension(s): `orgId`, `tokenId` * Data resolution: 40 seconds @@ -1425,37 +1473,21 @@ sf.org.numDatapointsDroppedThrottleByToken: metric_type: counter title: sf.org.numDatapointsDroppedThrottleByToken -sf.org.numDatapointsReceived: +sf.org.numDatapointsReceivedByMetricType: brief: Number of data points Infrastructure Monitoring received description: | - One value per metric type, each representing the number of data points that - Infrastructure Monitoring received and processed. - You can have up to three MTS for this metric. To - learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). - The sum of the values represents the total number of data points you sent to Infrastructure Monitoring minus any - data points that weren't accepted because you exceeded a limit. - -sf.org.numDatapointsReceivedByToken: - brief: Per token number of data points Infrastructure Monitoring received - description: | - One value per metric type per token, each representing the number - of data points Infrastructure Monitoring received and processed. The sum of values for a - token is the total number of data points you sent to Infrastructure Monitoring minus the number of - data points that Infrastructure Monitoring didn't accept because you exceeded a limit. - You can have up to three MTS for this metric. To learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). - The sum of all the values might be less than the value of `sf.org.numDatapointsReceived`. - To learn more, see [Metrics for values by token](#metrics-for-values-by-token). - * Data resolution: 1 second - metric_type: counter - title: sf.org.numDatapointsReceivedByToken - + One value per metric type, each representing the number of data points that Infrastructure Monitoring received and processed. + You can have up to four MTS for this metric, one for each metric type: gauge, counter, cumulative counter, and histogram. To learn more, see [Metrics with values for each metric type](#metrics-with-values-for-each-metric-type). + The sum of the values represents the total number of data points you sent to Infrastructure Monitoring minus any data points that weren't accepted because you exceeded a limit. + title: sf.org.numDatapointsReceivedByMetricType + sf.org.numDimensionObjectsCreated: brief: Number of dimensions created description: | Total number of dimensions created. + * Dimension(s): `orgId` - * Data resolution: 10 seconds - + * Data resolution: 10 seconds metric_type: gauge title: sf.org.numDimensionObjectsCreated @@ -1463,9 +1495,9 @@ sf.org.numDimensionObjectsCreatedByToken: brief: Number of dimensions created by token description: | Total number of dimensions created by token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds + * Dimension(s): `orgId`, `tokenId` + * Data resolution: 40 seconds metric_type: gauge title: sf.org.numDimensionObjectsCreatedByToken @@ -1473,9 +1505,9 @@ sf.org.numEventSearches: brief: Number of event searches description: | Number of event searches. - * Dimension(s): `orgId` - * Data resolution: 10 seconds - + + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numEventSearches @@ -1483,9 +1515,9 @@ sf.org.numEventSearchesThrottled: brief: Number of event searches that were throttled description: | Number of event searches that were throttled. - * Dimension(s): `orgId` - * Data resolution: 10 seconds - + + * Dimension(s): `orgId` + * Data resolution: 10 seconds metric_type: counter title: sf.org.numEventSearchesThrottled @@ -1577,9 +1609,9 @@ sf.org.numHostMetaDataEventsDroppedThrottle: brief: Number of host metadata events dropped due to throttling description: | Number of host metadata events dropped because of throttling. - * Dimension(s): `orgId` - * Data resolution: 40 seconds + * Dimension(s): `orgId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottle @@ -1587,9 +1619,9 @@ sf.org.numHostMetaDataEventsDroppedThrottleByToken: brief: Number of host metadata events dropped due to throttling by token description: | Number of host metadata events dropped because of throttling, per token. - * Dimension(s): `orgId`, `tokenId` - * Data resolution: 40 seconds + * Dimension(s): `orgId, tokenId` + * Data resolution: 40 seconds metric_type: counter title: sf.org.numHostMetaDataEventsDroppedThrottleByToken @@ -1710,9 +1742,9 @@ sf.org.numLogsReceivedByToken: brief: Number of logs received by token description: | Number of logs received by token. + * Dimension(s): `orgId`, `tokenId` * Data resolution: 10 seconds - metric_type: counter title: sf.org.numLogsReceivedByToken @@ -1785,9 +1817,9 @@ sf.org.numMetricObjectsCreatedByToken: brief: Number of metric objects created by token description: | Number of metric objects created by token. - * Dimension(s): `tokenId`, `orgId` - * Data resolution: 40 seconds + * Dimension(s): `tokenId`, `orgId` + * Data resolution: 40 seconds metric_type: gauge title: sf.org.numMetricObjectsCreatedByToken @@ -1816,9 +1848,9 @@ sf.org.numProcessDataEventsDroppedThrottleByToken: brief: Number of data ingest process events dropped due to throttling by token description: | Per token, number of data ingest process events dropped due to throttling, because you exceeded your system limits. + * Dimension(s): `orgId`, `tokenId` * Data resolution: 40 seconds - metric_type: counter title: sf.org.numProcessDataEventsDroppedThrottleByToken @@ -2071,7 +2103,7 @@ sf.org.ui.num.pagevisits: title: sf.org.ui.num.pagevisits sf.org.rum.numSpansReceived: - brief: The number of spans Splunk RUM accepts after filtering and throttling. + brief: The number of spans Splunk RUM accepts after discarding invalid and throttled spans. description: | Number of spans received. @@ -2082,10 +2114,10 @@ sf.org.rum.numSpansReceived: sf.org.rum.numSpansReceivedByToken: brief: The number of spans Splunk RUM received for a specific access token - after filtering and throttling. + after discarding invalid and throttled spans. description: | The number of spans Splunk RUM received for a specific access token - after filtering and throttling. + after discarding invalid and throttled spans. * Dimension: `orgId`, `tokenId` * Data resolution: 10 seconds @@ -2178,10 +2210,10 @@ sf.org.rum.numSpanBytesReceivedByToken: title: sf.org.rum.numSpanBytesReceivedByToken -sf.org.rum.grossSpanBytesReceivedByToken: - brief: The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. +sf.org.rum.grossSpanBytesReceivedByToken: + brief: The uncompressed bytes of all the spans received and counted by the metric grossSpansReceived for a specific access token before discarding invalid and throttled spans. This is a per token metric. description: | - The bytes (uncompressed) of all the spans received and counted by the metric grossSpansReceived before throttling or filtering by token. + The uncompressed bytes of all the spans received and counted by the metric grossSpansReceived for a specific access token before discarding invalid and throttled spans. This is a per token metric. * Dimensions: `orgId`, `tokenId` * Data resolution: 10 seconds @@ -2189,9 +2221,9 @@ sf.org.rum.grossSpanBytesReceivedByToken: title: sf.org.rum.grossSpanBytesReceivedByToken sf.org.rum.numContentBytesReceived: - brief: The volume of bytes Splunk RUM receives after filtering and throttling. + brief: The volume of bytes Splunk RUM receives after discarding invalid and throttled spans. description: | - The volume of bytes Splunk RUM receives after filtering and throttling. + The volume of bytes Splunk RUM receives after discarding invalid and throttled spans. * Dimensions: `orgId` * Data resolution: 10 seconds @@ -2219,3 +2251,13 @@ sf.org.rum.grossContentBytesReceived: metric_type: counter title: sf.org.rum.grossContentBytesReceived + +sf.org.rum.grossReplayContentBytesReceived: + brief: The possibly compressed wire size of the payloads before the payloads are decompressed and decoded, per RUM session replay. + description: | + The possibly compressed wire size of the payloads before the payloads are decompressed and decoded, per RUM session replay. + + * Dimensions: `orgId` + * Data resolution: 10 seconds + metric_type: counter + title: sf.org.rum.grossReplayContentBytesReceived