ENG-3333 : Apache druid integration for metrics #91
Conversation
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
bhogayatakb
changed the title
|
Add a common resource attributes for all the druid specific metrics so that we can add a type for bifrost > resourcewrapper |
Added common resource attribute. |
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
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.
Description:
Metric receiver for Apache Druid. Druid emits metrics over HTTP if enabled. Proposed is an HTTP server that takes this emitted metrics, and translates it to OTEL format.
The
internal/metadata.yamldoesn't serve the same purpose as in other receivers as we don't use it to make auto generated methods. This metadata has the info about the type of metric, its unit, and description. The piece of puzzle that is remaining is attributes.Currently we are sending the remaining fields in the json payload of the emitted metrics as attributes. Any ideas or suggestions regarding this are highly appreciated.
Link to tracking Issue:
ENG-3333