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

Alert: NodeSystemSaturation in monitoring #485

Open
paulfantom opened this issue May 7, 2024 · 0 comments
Open

Alert: NodeSystemSaturation in monitoring #485

paulfantom opened this issue May 7, 2024 · 0 comments
Labels
alert/new Issue created due to warning alert firing

Comments

@paulfantom
Copy link
Member

paulfantom commented May 7, 2024

Alert NodeSystemSaturation firing in monitoring namespace

This is an automated issue created by the monitoring system. Please do not edit this message.

Alertmanager URL: https://alertmanager.ankhmorpork.thaum.xyz

Issue was last updated at 2024-12-21 01:31:41.824312433 +0000 UTC m=+3538.444815316.

Common Labels

alertname NodeSystemSaturation
cluster ankhmorpork
container kube-rbac-proxy
endpoint https
instance master01
job node-exporter
namespace monitoring
node master01
pod node-exporter-ssh9m
prometheus monitoring/k8s
service node-exporter
severity warning

Common Annotations

description System load per core at master01 has been above 2 for the last 15 minutes, is currently at 2.21. This might indicate this instance resources saturation and can cause it becoming unresponsive.
runbook_url https://runbooks.thaum.xyz/runbooks/node/nodesystemsaturation
summary System saturated, load per core is very high.

Alerts

StartsAt Links
2024-12-21 00:46:09.939 +0000 UTC GeneratorURL
@paulfantom paulfantom added the alert/new Issue created due to warning alert firing label May 7, 2024
@paulfantom paulfantom reopened this Nov 30, 2024
@paulfantom paulfantom reopened this Dec 1, 2024
@paulfantom paulfantom reopened this Dec 1, 2024
@paulfantom paulfantom reopened this Dec 1, 2024
@paulfantom paulfantom reopened this Dec 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
alert/new Issue created due to warning alert firing
Projects
None yet
Development

No branches or pull requests

1 participant