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.

Sign up for GitHub

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

Jump to bottom

Automatic setup of exporting driver metrics to Prometheus #255

Closed
2 tasks done
liyinan926 opened this issue Aug 12, 2018 · 0 comments
Closed
2 tasks done

Automatic setup of exporting driver metrics to Prometheus #255

liyinan926 opened this issue Aug 12, 2018 · 0 comments
Labels
enhancement New feature or request
Milestone
beta

Comments

@liyinan926
Copy link
Collaborator

liyinan926 commented Aug 12, 2018 •
edited
Loading

Metrics of the drivers can be exposed through JMX using the JmxSink, and then exported to Prometheus through the Prometheus JMX exporter. The Prometheus configuration file needed by the JMX exporter can be generated by the operator and automatically mounted into the driver pod through a ConfigMap. Then the annotation prometheus.io/scrape=true should make the Prometheus server to scrape the metrics exposed by the driver pods.

  • Implementation.
  • Documentation.
@liyinan926 liyinan926 added the enhancement New feature or request label Aug 12, 2018
This was referenced Aug 16, 2018
Merged
Merged
Closed
Closed
liyinan926 added a commit to liyinan926/spark-on-k8s-operator that referenced this issue Aug 20, 2018
@liyinan926
Added documentation for kubeflow#255
30cde81
@liyinan926 liyinan926 mentioned this issue Aug 20, 2018
Merged
liyinan926 added a commit that referenced this issue Aug 20, 2018
@liyinan926
Added documentation for #255
c07b040
@liyinan926 liyinan926 added this to the beta milestone Aug 23, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
beta
Development

No branches or pull requests
1 participant
@liyinan926