forked from open-telemetry/opentelemetry-collector-contrib
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Datadog k8 Metrics reciever Added #76
Closed
Closed
+26,694
−4,679
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
* ENG-833: Fixed k8s.pod.start_time metrics for k8s.pod * ENG-1067: Added k8s.pod.filesystem.utilization, k8s.node.filesystem.utilization & container.filesystem.utilization metrics; ENG-1076: Added k8s.job.uid & k8s.job.name for job <> pod mapping. * Test-cases for ENG-1076 & previous functions * Autogenerated files re-uploaded * ENG-947 & ENG-1241: Added Persistent-Volume Flow
Loading status checks…
…ow (#43)
* normalised statement counts, cumulative time per statement * changed to event time limit to be maxInt64 * removed print statements * nit * Update go.mod * enabled statement event time * small fix * Added count-star datapoint
* ENG-2454: AWS Integration * minor
* ENG-2454: AWS Integration * minor * ENG-2454: AWS Integration - Minor Changes
* Update cloudwatchreceiver to use aws sdk v2 and role delegation * Add middleware.io specific resource attributes for cloudwatchreceiver
meenal-developer
approved these changes
Jun 25, 2024
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.
DONT MERGE Testing in progress
Title: Add Kubernetes Datadog Metric Receiver
Description:
This PR introduces a new Kubernetes Datadog metric receiver to enhance our monitoring capabilities. Key changes and features include:
Kubernetes Datadog Metric Receiver:
Enhanced Correlation:
Modular Structure:
Added all Apis of datadog agent and attached not implemented Handler if we are not currently implementing
Some Dummy Metrics are Introduced to Capture Information
Future Scope ( V2 Metric Classifier ) better approach and add missing unit tests
One thing is pending As in kubernetes state metrics
Host Name is Node/Host name + cluster Name
Already Raised a support ticket if we can get only host name as in Other
Kubernetes Metrics we are getting Host Name only