You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://github.com/DataDog/datadog-agent/blob/main/pkg/config/config_template.yaml#L199-L200
Customers occasionally run into issues caused by using low cardinality for this on Fargate where metrics get 'squashed' together due to having identical timestamps and tags. When this happens, it often leads to lengthy investigations to determine why metric values are a bit lower than expected
Merge instructions
Merge readiness:
Ready for merge
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the <yourname>/description naming convention) and then add the following PR comment:
2025-01-17 21:56:12 UTC ℹ️ MergeQueue: waiting for PR to be ready
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals. Note: if you pushed new commits since the last approval, you may need additional approval.
You can remove it from the waiting list with /remove command.
2025-01-17 22:41:07 UTC⚠️MergeQueue: This merge request was unqueued
@JakeYankovich I noticed this wasn't building, and realized it was because your branch name didn't have a slash in it, as per our branch naming convention. I know you wanted to get this out quickly, so I duplicated your change in a different PR (#27191) and am publishing it now. Sorry for the inconvenience!
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
dd-devflow
bot
added
mergequeue-status: removed
and removed
mergequeue-status: waiting
labels
What does this PR do? What is the motivation?
This PR adds a couple notes about the pros and cons of the different options for
DD_DOGSTATSD_TAG_CARDINALITYsources:
Customers occasionally run into issues caused by using
lowcardinality for this on Fargate where metrics get 'squashed' together due to having identical timestamps and tags. When this happens, it often leads to lengthy investigations to determine why metric values are a bit lower than expectedMerge instructions
Merge readiness:
Merge queue is enabled in this repo. To have it automatically merged after it receives the required reviews, create the PR (from a branch that follows the
<yourname>/descriptionnaming convention) and then add the following PR comment:Additional notes