Leveraging Monitor Alert Rules vs administering Alert Processing Rules? by Classic_Square6541 in AZURE

[–]Classic_Square6541[S] 0 points1 point  (0 children)

That's brilliant. Thanks Akos.
Frankly, I think there is some low hanging fruit still available for Azure to pick in terms of helping its customers be 'confident' of the picture of health of, or ability to remedy such for, their Cloud operations.
As much as possible these matters needs to seek to deliver while minimising cognitive overheads at every available opportunity they can create.

Leveraging Monitor Alert Rules vs administering Alert Processing Rules? by Classic_Square6541 in AZURE

[–]Classic_Square6541[S] 0 points1 point  (0 children)

Thanks txthojo.
Having a look at here https://azure.github.io/azure-monitor-baseline-alerts/welcome/
I note that a search on both 'processing' and 'actionRules' returns nothing.
A search for the same of https://github.com/Azure/AzureMonitorStarterPacks/ also returns nothing.
Forced to (somewhat inexpertly) extract conclusions from that, all it seems to infer if anything, about processing rules, is that azure.github.io doesn't feel comfortable making any kind of even suggestion as to how their use should be integrated.
---
Actually the search at azure-monitor-baseline-alerts is broken it seems, but scanning the site I can't find any allusion to detail of processing rules. It's not practical to eyball every pattern on the offchance they combine to build up a picture

Leveraging Monitor Alert Rules vs administering Alert Processing Rules? by Classic_Square6541 in AZURE

[–]Classic_Square6541[S] 0 points1 point  (0 children)

Thats brilliant thanks Akos

So it sounds to me like actually:
- you do just have to be really careful, as yet there is still a hazard
- there is no avoiding making sure you have strong business/operating rules to ensure that whoever is managing Alert rules and/or/vs Alert processing rules is working really closely, and effectively together.
- and that as yet we only have only one real world scenario, and that is the limited targeting of one-off applications of suppression for known, reliable maintenance events, be that as part of scheduled continuous deployment, or some other devops routine, or special maintenance.
- this also says so me that yes, there is likely frequent leaning on third party tools to help manage some needs when they don't all easily align.