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: Databricks Receiver #18724

Open
2 tasks
pmcollins opened this issue Feb 16, 2023 · 7 comments
Open
2 tasks

New component: Databricks Receiver #18724

pmcollins opened this issue Feb 16, 2023 · 7 comments
Labels

Comments

@pmcollins
Copy link
Member

pmcollins commented Feb 16, 2023

The purpose and use-cases of the new component

The Databricks Receiver uses the Databricks API to generate metrics about the operation of a Databricks instance.

In addition to generating metrics from the Databricks API, it also generates metrics from the Spark subsystem running in a Databricks instance.

Example configuration for the component

databricks:
  instance_name: my-instance
  endpoint: https://dbr.example.net
  token: abc123
  spark_org_id: 1234567890
  spark_endpoint: https://spark.example.net
  spark_ui_port: 40001
  collection_interval: 10s

Telemetry data types supported

Metrics

Is this a vendor-specific component?

  • This is a vendor-specific component
  • If this is a vendor-specific component, I am proposing to contribute this as a representative of the vendor.

Sponsor (optional)

No response

Additional context

An early implementation is here. We would like to donate this to the community.

@pmcollins pmcollins added the needs triage New item requiring triage label Feb 16, 2023
@dmitryax
Copy link
Member

I'll sponsor this receiver

@dmitryax dmitryax added Accepted Component New component has been sponsored and removed needs triage New item requiring triage labels Feb 16, 2023
@pmcollins
Copy link
Member Author

Thank you Dmitrii!

@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 Apr 18, 2023
@dmitryax dmitryax removed the Stale label Apr 18, 2023
@atoulme atoulme mentioned this issue May 8, 2023
2 tasks
@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 Jun 19, 2023
@github-actions
Copy link
Contributor

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 Aug 18, 2023
@tejalchandekar1996
Copy link

Is this receiver added yet? If not, how can i import the receiver and build my own collector? Can someone please help me with it?

@crobert-1
Copy link
Member

I will work to contribute this component. @dmitryax can you confirm that you're still able to sponsor this?

@crobert-1 crobert-1 reopened this Jan 10, 2025
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