seems there're 2 hardcoded namespace in the yaml file

[GuopingYe]

There're 2 alerting rules showing "no data" on my end, I went through the rules and find there're some issues on the yaml file,

monitoring/alerting/rules/viya_platform_alerts.yaml
monitoring/rules/viya/beta-rules-viya-health.yaml

BTW, 2 more questions,

1. I'm not sure if it's due to SAS deployment update, some rules like "High API Latency" shows no data too, and I found the metric specified in the yaml file does not exists.

2. I'm not sure if expression language was updated on Grafana or not, like "CAS Thread Count High" with query "cas_grid_sessions_current > 400" returns no data even "cas_grid_sessions_current“ do has data itself, I need to manualy split this expression into 2 part, first query A = cas_grid_sessions_current, then add a threshold B as "A > 400", then set B as alert condition, then it works as expected.

[gsmith-sas]

@GuopingYe Thank you for reporting these issues and our apologies for any inconvenience they may have caused.

With regard to the monitoring/rules/viya/beta-rules-viya-health.yaml file: this is an obsolete file that should have been deleted from the repo. We will be doing so in the next few days. In the meantime, you should ignore the file and its contents.

With regard to the hard-coded reference to the namespace in the Viya Pod Restart Count High alert (defined in monitoring/alerting/rules/viya_platform_alerts.yaml file), the easiest fix would be to update that file with the name of the namespace in which you have deployed SAS Viya and then redeploy the metric monitoring stack.

We are looking into the other issues and will report back when we've identified the best way to resolve things.

Regards,
Greg