-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Support Prometheus PodMonitor Deployment #1106
Comments
Hi, |
GCP Spark Operator does not deploy a |
@fisache , thank you for the response. |
Hi!
May be we should think of creation of such service ?
It will be nice to optionally submit pod(service)monitor for spark operator during deployment via helm chart. |
for a Spark application(driver and executor pods) |
Right, but our suggestion is to support pod/service monitor configuration (and optional submission via helm chart) for the Spark operator itself, not for the applications. |
@liyinan926 , do you see some value in adding pod(service) monitor for operator pod ? If so, we can open a PR with changes. |
I was confused. The operator's monitoring using prometheus-operator seems to be essential :) |
* Supported Prometheus monitoring via pod monitor for the Spark operator's pod. * Added Prometheus `metrics.portName` to use it for `podMonitor.podMetricsEndpoint` configuration, becuse `targetPort` has been deprecated by Prometheus.
* Upgrade the Chart version number.
* Supported Prometheus monitoring via pod monitor for the Spark operator's pod. * Added Prometheus `metrics.portName` to use it for `podMonitor.podMetricsEndpoint` configuration, becuse `targetPort` has been deprecated by Prometheus.
* Upgrade the Chart version number.
Hello,
Could you please support Prometheus PodMonitor configuration and deployment for Spark Operator?
Currently the Spark GCP Operator exposes metrics endpoint, but there is no ability to configure Prometheus integration.
The text was updated successfully, but these errors were encountered: