Skip to content
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

New component: Add Apache Druid Metric Receiver #8466

Closed
rahulbandariSensei opened this issue Mar 15, 2022 · 4 comments
Closed

New component: Add Apache Druid Metric Receiver #8466

rahulbandariSensei opened this issue Mar 15, 2022 · 4 comments
Assignees
Labels

Comments

@rahulbandariSensei
Copy link

The purpose and use-cases of the new component

Apache Druid Receiver(apachedruid) listens on for the metrics emitted by the apache druid endpoint as mentioned in metrics page and generates all the metrics related to different sub-components of a druid cluster.

Example configuration for the component

receivers:
   apachedruid:
    emitterport: 8911

Telemetry data types supported

Metrics Emitted by the apache druid (https://druid.apache.org/docs/latest/operations/metrics.html) would be supported here.
Will update the names shortly.

@mx-psi mx-psi added the Sponsor Needed New component seeking sponsor label Mar 15, 2022
@dmitryax
Copy link
Member

I can sponsor this component. I have experience with Druid

@dmitryax dmitryax removed the Sponsor Needed New component seeking sponsor label Jul 20, 2022
@dmitryax
Copy link
Member

@rahulbandariSensei feel free to submit PRs. I'll be reviewing them

@codeboten codeboten added the Accepted Component New component has been sponsored label Sep 16, 2022
@github-actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Nov 16, 2022
@github-actions
Copy link
Contributor

github-actions bot commented May 5, 2023

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants