Fixed alert reporting, instance label, gitea limits
Update Kubernetes Services Wiki / Generate and Update K8s Wiki (push) Successful in 29s
Update Kubernetes Services Wiki / Generate and Update K8s Wiki (push) Successful in 29s
This commit is contained in:
1 parent
ac8e5e127c
commit
f2d5b97465
4 files changed
+57
-19
No files matched your search
@@ -36,6 +36,17 @@ them. This protects data from a manifest rename, but it is not a backup. Back up
|
||||
custom fields `IDM Client ID`, `IDM Client Secret`, `TG Token`, and `TG ID`;
|
||||
- DNS for `gf.hexor.cy` and `prom.hexor.cy` must point to the new cluster.
|
||||
|
||||
## Alerting and target identities
|
||||
|
||||
Telegram is reserved for actionable alerts: `severity=info`, `Watchdog`, and
|
||||
`InfoInhibitor` remain visible in Prometheus but route to the null receiver.
|
||||
Warning and critical notifications are grouped for two minutes and rendered as
|
||||
Telegram HTML with escaped annotations and labelled graph/runbook links.
|
||||
|
||||
Node Exporter keeps scraping the discovered node address, but rewrites the
|
||||
public `instance` label from Kubernetes discovery to `<node-name>:9100`. Grafana
|
||||
variables and alerts therefore remain stable when node IP addresses change.
|
||||
|
||||
After Argo CD reports the application healthy, verify targets, rules and log
|
||||
delivery in Grafana. Prometheus is protected by the Keycloak auth proxy; Grafana
|
||||
uses its own Keycloak OIDC client.
|
||||
Reference in new issue
Block a user