Azure / azure-monitor-baseline-alerts

Azure Monitor Baseline Alerts
MIT License
165 stars 241 forks source link

[Question/Feedback]: Ability to update the Action Group displayname/shortname #144

Closed carlzxc71 closed 8 months ago

carlzxc71 commented 8 months ago

Check for previous/existing GitHub issues

Description

In the scenario where we receive alerts from several different customers & tenants we would like to be able to assign another displayname of the Action Group that is deployed with AMBA. This lets us know which tenant and customer the alert belongs to which is helpful since we have several different environments we are monitoring.

Is there a way to modify this today?

The way I have solved it so far is to run AZ CLI on a scheduled basis which updates the Displayname incase a new deployment has happened and a new action group has been created with the default ActGrp displayname we have today.

ID=$(az monitor action-group list --query "[?name.contains(@,'AMBA')].id" --output tsv)
az monitor action-group update --ids $ID --group-short-name "<customer shortname>"
Brunoga-MS commented 8 months ago

Hello @carlzxc71 , thanks for your feedback. In the latest release 2024-03-01 we changed the action group and alert processing rules display names to include both AMBA and the subscription display name. Unfortunately it is not possible to do too much on the short name since it is limited to 12 characters, so we cannot follow the same approach.

Thanks, Bruno.

carlzxc71 commented 8 months ago

Hello @carlzxc71 , thanks for your feedback. In the latest release 2024-03-01 we changed the action group and alert processing rules display names to include both AMBA and the subscription display name. Unfortunately it is not possible to do too much on the short name since it is limited to 12 characters, so we cannot follow the same approach.

Thanks, Bruno.

Hello & thank you for your response @Brunoga-MS

Unfortunately having the subscription name does not solve our problem since we do not use customers names in the displayname of subscriptions and in the scenario where several customers can run similar workloads such as ARC or AVD they can possible have the same name.

Our wish is being able to update the displayname of the actiongroup and if that is not possible today maybe we can add that to a "wishlist"?

We can run our script in the meantime but we would rather have the ability to configure everything in the same solution ofcourse.

Brunoga-MS commented 8 months ago

Hello @carlzxc71 , I cannot assure that we will add a parameter for the customer name to be used in the APRs/AGs but I will investigate. What about adding the customer name as Tag.

Thanks, Bruno.

carlzxc71 commented 8 months ago

Hello @carlzxc71 , I cannot assure that we will add a parameter for the customer name to be used in the APRs/AGs but I will investigate. What about adding the customer name as Tag.

Thanks, Bruno.

Understood. I am afraid that tags does not solve our issue as it does not appear in the email from Azure Monitor to my knowledge.

Brunoga-MS commented 8 months ago

Hello @carlzxc71 , I cannot assure that we will add a parameter for the customer name to be used in the APRs/AGs but I will investigate. What about adding the customer name as Tag. Thanks, Bruno.

Understood. I am afraid that tags does not solve our issue as it does not appear in the email from Azure Monitor to my knowledge.

They do not unless you use a custom email template through Logic App where you can modify/enrich the email body

carlzxc71 commented 8 months ago

Hello @carlzxc71 , I cannot assure that we will add a parameter for the customer name to be used in the APRs/AGs but I will investigate. What about adding the customer name as Tag. Thanks, Bruno.

Understood. I am afraid that tags does not solve our issue as it does not appear in the email from Azure Monitor to my knowledge.

They do not unless you use a custom email template through Logic App where you can modify/enrich the email body

I will look into that, thank you.

Brunoga-MS commented 8 months ago

Closing this one not in our plan to implement that.