-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[apm] standardize peer tag aggregation #20550
Changes from 30 commits
4d6faa4
bfb13e6
d25c225
e570487
9651de3
92adb54
aa88f6e
c484fa6
400cb60
1e59bed
12b1cb2
1597550
b253320
47c84b3
fc01656
1f4037f
ece387c
4933933
5d2a44b
ce3e6af
c4a643a
6ffb5db
ee35a7d
9e2c25f
d7cf0bf
93b6441
a34803e
0bcc362
368559d
236db04
c34a69d
4f4546e
26bc7ff
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1502,19 +1502,30 @@ api_key: | |
|
||
## @param peer_service_aggregation - bool - default: false | ||
## @env DD_APM_PEER_SERVICE_AGGREGATION - bool - default: false | ||
## [BETA] Enables `peer.service` aggregation in the agent. If disabled, aggregated trace stats will not include `peer.service` as a dimension. | ||
## DEPRECATED - please use `peer_tags_aggregation` instead. | ||
## Enables `peer.service` aggregation in the Agent. If disabled, aggregated trace stats will not include `peer.service` as a dimension. | ||
## For the best experience with `peer.service`, it is recommended to also enable `compute_stats_by_span_kind`. | ||
## If enabling both causes the Agent to consume too many resources, try disabling `compute_stats_by_span_kind` first. | ||
## If the overhead remains high, it will be due to a high cardinality of `peer.service` values from the traces. You may need to check your instrumentation. | ||
## NOTE: If you are using an OTel tracer it's best to have both enabled because client/producer spans with a `peer.service` value | ||
## may not be marked by the Agent as top-level spans. | ||
# peer_service_aggregation: false | ||
|
||
## @param peer_tags_aggregation - bool - default: false | ||
## @env DD_APM_PEER_TAGS_AGGREGATION - bool - default: false | ||
## [BETA] Enables aggregation of peer related tags (e.g., `peer.service`, `db.instance`, etc.) in the Agent. | ||
## If disabled, aggregated trace stats will not include these tags as dimensions on trace metrics. | ||
## For the best experience, Datadog also recommends enabling `compute_stats_by_span_kind`. | ||
## If enabling both causes the Agent to consume too many resources, try disabling `compute_stats_by_span_kind` first. | ||
## If the overhead remains high, it will be due to a high cardinality of peer tags from the traces. You may need to check your instrumentation. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. What should they be looking for in their instrumentation? Can we link them any documentation here? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can provide some more guidance in this comment. We do not have clear documentation that would speak to this specific concern. |
||
## NOTE: If you are using an OTel tracer, it's best to have both enabled because client/producer spans with a `peer.service` value | ||
## may not be marked by the Agent as top-level spans. | ||
# peer_tags_aggregation: false | ||
|
||
## @param peer_tags - list of strings - optional | ||
## @env DD_APM_PEER_TAGS - list of strings - optional | ||
## [BETA] Enables additional tags related to peer.service. Will not be used unless peer_service_aggregation is also set. | ||
## NOTE: This option is recommended to get the most granular tagging alongside `peer.service`, but it will | ||
## also increase the computational overhead of aggregation. This list can be omitted if that cost is too high for your agent. | ||
## [BETA] Optional list of supplementary peer tags that go beyond the defaults. The Datadog backend validates all tags | ||
## and will drop ones that are unapproved. | ||
# peer_tags: [] | ||
|
||
## @param features - list of strings - optional | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Presumably we recommend enabling
compute_stats_by_span_kind
ifpeer_tags_aggregation
is enabled?Do we recommend enabling
peer_tags_aggregation
?Will people reading this know what it means?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll rephrase. The idea here is that if you're using
peer_tags_aggregation
, you will likely also want the span kind flag enabled too.