-
Notifications
You must be signed in to change notification settings - Fork 10
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
Prometheus alerts mapping #34
Comments
List of Prometheus alerts:
|
@aleksandra-galara Thanks for preparing the list. Very helpful! 👍 Let's keep it up to date as the support for new alerts is added to the mapping. In the next iteration we should focus on the following items:
|
Hi, |
@aleksandra-galara Good work! I look forward to the first commits 😉 |
It refers to openrca#34 and complete mapping alerts due to list created in issue
Hi, I've mapped the alerts due to updated list of Prometheus alerts:
|
It refers to openrca#34 and complete mapping alerts due to list created in issue Signed-off-by: Aleksandra Galara <a.galara@samsung.com>
It refers to openrca#34 and complete mapping alerts due to list created in issue It introduces the changes suggested in the review Signed-off-by: Aleksandra Galara <a.galara@samsung.com>
It refers to openrca#34 and complete mapping alerts due to list created in issue. It introduces the changes suggested in the review Signed-off-by: Aleksandra Galara <a.galara@samsung.com>
It refers to openrca#34 and complete mapping alerts due to list created in issue. It introduces the changes suggested in the review Signed-off-by: Aleksandra Galara <a.galara@samsung.com>
Closing, because all alerts from the above list have been mapped. The ones awaiting mapping improvement are tracked by #58. |
It implements openrca#34 Signed-off-by: Aleksandra Galara <a.galara@samsung.com>
Prometheus provides a comprehensive set of alerting rules for Kubernetes such as:
KubeContainerWaiting
KubeDaemonSetNotScheduled
KubeAPIErrorsHigh
Open RCA enables connecting some of these alerts to elements present in the infra graph by using a mapping file. The entries in the file are of the form:
The example above describes that whenever there is a
KubePodCrashLooping
alert detected, it should be mapped to graph element ofkubernetes
origin andpod
kind, and connected to an element with propertiesname
andnamespace
with values fetched from labels in alert payload, named correspondinglypod
andnamespace
.The mapping file is not complete. There is still a significant number of alerts that Open RCA cannot recognize. The remaining alerting rules should be reviewed and integrated into the mapping.
The text was updated successfully, but these errors were encountered: