Skip to content

spark-operator: Document how to monitor with jmx and prometheus #4098

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fjammes
Copy link

@fjammes fjammes commented May 2, 2025

Checklist:

  • [ X] You have signed off your commits
  • [ X] Ensure you follow best practices from our guide. Contributing.
  • [] You have included screenshots when changing the website style or adding a new page.
    (not able to locally build the website because of below error:
    $ hugo server -D
    Error: html/template:_partials/head.html:73:16: no such template "_internal/google_analytics_async.html"
    $ hugo version
    hugo v0.147.1+extended+withdeploy linux/amd64 BuildDate=unknown
    )

Description of your changes: Document how to setup spark monitoring with JMX and Prometheus

Labels

/area spark-operator

/area website


@google-oss-prow google-oss-prow bot added area/spark-operator AREA: Kubeflow Spark Operator area/website AREA: Website Styles/Hosting/Serving labels May 2, 2025
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chenyi015 for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link

Hi @fjammes. Thanks for your PR.

I'm waiting for a kubeflow member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Copy link
Member

@Arhell Arhell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/ok-to-test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/spark-operator AREA: Kubeflow Spark Operator area/website AREA: Website Styles/Hosting/Serving ok-to-test size/L
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants