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

[RFE] Update UI to allow enabling metrics for Backup&Restore Operator #13513

Open
jbiers opened this issue Feb 25, 2025 · 0 comments
Open

[RFE] Update UI to allow enabling metrics for Backup&Restore Operator #13513

jbiers opened this issue Feb 25, 2025 · 0 comments
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone

Comments

@jbiers
Copy link
Member

jbiers commented Feb 25, 2025

The O&B team has implemented metrics for the Backup&Restore Operator. These can currently be enabled via Helm Charts by setting these values to true:

monitoring:
  metrics:
    enabled: false

  serviceMonitor:
    enabled: false

We also want users to be able to set these via UI in cluster tools --> rancher-backup --> step 2 (the screen shown in the image):
Image

Ideally we'd see another section below the existing "Default Storage Location" named "Monitoring". In this new section we should have the ability to turn on the metrics (Values.monitoring.metrics.enabled) and the serviceMonitor
(Values.monitoring.serviceMonitor.enabled), each independently of the other. Also, the user should only be allowed to enable the serviceMonitor via UI if rancher-monitoring is installed.

Additional context
rancher/backup-restore-operator#648

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Feb 25, 2025
@jbiers jbiers added this to the v2.12.0 milestone Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Development

No branches or pull requests

1 participant