Mark Allen
My feedback
-
51 votes
Thanks for your feedback. Adding parameters to saved functions is definitely something we would consider for the future.
An error occurred while saving the comment Mark Allen
supported this idea
·
-
48 votesunder review · 7 comments · Azure Monitor- Alert Management » Configuring Alerts · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Mark Allen
commented
The previous commenters have captured the use case well. In synopsis, we are simply trying to create "inactivity" alerts, that allow us to see when customer activity has stopped today based on prior days activity. It is infeasible to maintain a whitelist of customers to monitor, so instead we auto-discover prior customer activity (i.e. establish activity baseline) and then compare today's activity to that baseline. For us, customer activity is minimal to non-existent over the weekends, so on Monday, a 2 day limit on the query window will not allow us to see workday activity from Friday. Hence, these customers would not be identified as inactive because they have fallen out of the baseline, and then going forward, they will also be missed because the baseline will no longer capture them.
If you are trying to balance alert load, possibly more expensive alerts could be a premium feature with dedicated capacity (similar to how Azure Service Bus allows for Premium queue storage)?
Mark Allen
supported this idea
·
As we seek to build out a robust library of queries, the inability to use parameterized shared functions causes serious maintainability issues for us. This manifests as copy-paste in many of our shared queries, and if that function logic needs to change, significant updates to many queries.