-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Comments
I'll sponsor this receiver |
Thank you Dmitrii! |
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 |
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 |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
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? |
I will work to contribute this component. @dmitryax can you confirm that you're still able to sponsor this? |
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
Telemetry data types supported
Metrics
Is this a vendor-specific component?
Sponsor (optional)
No response
Additional context
An early implementation is here. We would like to donate this to the community.
The text was updated successfully, but these errors were encountered: