Skip to content

Commit f43585e

Browse files
committed
update alert samples readme
1 parent c4d3d3c commit f43585e

File tree

1 file changed

+14
-4
lines changed

1 file changed

+14
-4
lines changed

samples/alerts/README.md

Lines changed: 14 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -43,10 +43,6 @@ groups:
4343
uid: unique-alert-id # Unique identifier for the alert
4444
```
4545
46-
## Legacy Alert Files
47-
48-
The original monolithic alert files (cas_alerts.yaml, database_alerts.yaml, etc.) are still present for backward compatibility. These files will be deprecated in future releases, so we recommend using the individual alert files going forward.
49-
5046
## Customizing Alerts
5147
5248
To customize an alert:
@@ -55,4 +51,18 @@ To customize an alert:
5551
2. Modify the alert parameters as needed (thresholds, evaluation intervals, etc.)
5652
3. Deploy the monitoring components to apply your custom alerts
5753
54+
### Common Customizations Needed
55+
56+
#### Namespace Adjustments
57+
Some alerts reference specific namespaces that need to be adjusted for your environment:
58+
- In several rules (like `viya-pod-restart-count-high.yaml`), the namespace is set to "viya" with `namespace="viya"`. Change this to match your SAS Viya namespace.
59+
60+
#### Alert Expression Format
61+
Alert expressions in these samples use a multi-part approach for better compatibility with newer Grafana versions:
62+
- Part A: Fetches the raw metric
63+
- Part B: Reduces the result (using the "reduce" function)
64+
- Part C: Applies the threshold using a dedicated threshold component
65+
66+
This approach addresses issues where direct threshold comparisons (e.g., `metric > threshold`) might not work properly in recent Grafana versions.
67+
5868
For more detailed information on Grafana alerting, see the [Grafana documentation](https://grafana.com/docs/grafana/latest/alerting/).

0 commit comments

Comments
 (0)