Skip to content

Commit

Permalink
Resolve merge conflicts
Browse files Browse the repository at this point in the history
  • Loading branch information
trangl-splunk committed May 6, 2024
1 parent e5d89f3 commit bd21b5f
Showing 1 changed file with 0 additions and 8 deletions.
8 changes: 0 additions & 8 deletions signalfx-org-metrics/metrics.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -133,15 +133,11 @@ 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: |
<<<<<<< HEAD
The number of spans that APM was unable to process or has dropped because the trace has a blocked trace ID or too many spans in the trace.
=======
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:
>>>>>>> main
* Dimension(s): `orgId`
* Data resolution: 1 second
Expand All @@ -151,16 +147,12 @@ 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: |
<<<<<<< HEAD
The number of spans for a specific token that APM was unable to process or has dropped because the trace has a blocked trace ID or too many spans in the trace.
=======
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:
>>>>>>> main
* Dimension(s): `orgId`
* Data resolution: 1 second
Expand Down

0 comments on commit bd21b5f

Please sign in to comment.