Support for DataDog SDK dashboards and conf.yaml support. Doc improvements #70
Conversation
This file contains hidden or 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
antmendoza
approved these changes
Aug 30, 2025
Member
There was a problem hiding this comment.
Thanks @mnichols
This is super useful.
Another consideration, histogram metrics from Java and Go are emitted with prefix *_second
We could add a note mentioning that the user needs to change the query, or make it explicit that this dashboard is only for core-based SDKs
Contributor
Author
|
@antmendoza I agree the distinction among SDK lineage for metric format is a important call out. Maybe that should be front and center overall in this repo instead of just DD? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was changed
DataDogdashboard, config and docs where appropriate. Tried to make it easy to get up and running with DD by linking to related resources.Why?
We have a bajillion DataDog customers and we need to flip them a bone 😼 . Also, we should make these kinds of integrations easy to discover and pull together.
Checklist
How was this tested:
I ran alot of load through
omesand messed with Worker configs to trip certain metrics, as well as screwing with WF code to trip NDEs and so on. They-axeson these should be ok but improvements can no doubt me made over time.Any docs updates needed?
No, this is a document update and I'm afraid I would fall into a wormhole if I said "yes".