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

Monitoring and Alerting requirements for existing managed stack #357

Closed
7 of 9 tasks
Tracked by #555
VaishnaviHire opened this issue Jul 21, 2023 · 5 comments
Closed
7 of 9 tasks
Tracked by #555
Assignees
Labels
enhancement New feature or request needs-qe-verification rhods-2.4 Tracker Non-completable ticket; used for tracking work at a high level

Comments

@VaishnaviHire
Copy link
Member

VaishnaviHire commented Jul 21, 2023

This is a tracker issue to capture requirements, changes for Monitoring stack

Requirements

  • Migrate all alerting and monitoring resources from odh-deployer
  • Setup alerts only when a component is in Managed state
  • Scope changes required to move to new monitoring stack.
  • Identify new components and additional alerts required.

Changes

@VaishnaviHire VaishnaviHire added the enhancement New feature or request label Jul 21, 2023
@zdtsw
Copy link
Member

zdtsw commented Jul 24, 2023

ref: #341

@zdtsw
Copy link
Member

zdtsw commented Sep 28, 2023

looks like in prometheusv2.43.0https://github.com/prometheus/prometheus/releases/tag/v2.43.0 the feature has been added to support "scrape_config_files"
but the "latest" image we can use registry.redhat.io/openshift4/ose-prometheus@sha256:2572eff86dc111203c5de6ce7325cc061ddb4bd737e09a1639313f3a9ed07a9c was built off 2.42.0

@VaishnaviHire VaishnaviHire changed the title Monitoring and Alerting requirements tracker Monitoring and Alerting requirements for existing managed stack Oct 5, 2023
@zdtsw
Copy link
Member

zdtsw commented Oct 11, 2023

after a first test with QE, some parts need to figure:

@VaishnaviHire
Copy link
Member Author

Hi @zdtsw for -

when user update notification mail, how this will be reflact to the configmap? need to understand how v1 did this

This will be a separate PR that should add the changes to watch the addn-parameters configmap. For v1 operator the change was added here - red-hat-data-services#133

@VaishnaviHire
Copy link
Member Author

@zdtsw Can we close this as completed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request needs-qe-verification rhods-2.4 Tracker Non-completable ticket; used for tracking work at a high level
Projects
Status: Done
Development

No branches or pull requests

3 participants