Skip to content
This repository has been archived by the owner on May 7, 2024. It is now read-only.

UserStory30082-Migration-ClassicAlerts #119

Closed
wants to merge 0 commits into from

Conversation

Poven795909
Copy link
Contributor

Overview/Summary

UserStory30082-Migration-ClassicAlerts

This PR fixes/adds/changes/removes

  1. Adds recommendations for Classic alerts migration
  2. Adds formatting change

@oZakari oZakari closed this Oct 17, 2023
@oZakari oZakari reopened this Oct 17, 2023
| extend isUsingClassicAlerts = case(isnull(monitoringSettings), 'Enabled',monitoringSettings.classicAlertSettings.alertsForCriticalOperations)
| extend isUsingJobsAlerts = case(isnull(monitoringSettings), 'Enabled', monitoringSettings.azureMonitorAlertSettings.alertsForAllJobFailures)
| where isUsingClassicAlerts == 'Enabled'
| project recommendationId = "bk-1",name,resourceGroup,location,type,id,isUsingClassicAlerts,isUsingJobsAlerts
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @Poven795909, looks good overall, just one small change and then we should be able to merge. Could you please adjust the columns returned to only the ones listed here

You could adjust to something like the following as an example: | project recommendationId = "bk-1", name, id, param1=strcat(isUsingClassicAlerts: ", isUsingClassicAlerts), param2=strcat("isUsingJobsAlerts: ", isUsingJobsAlerts)

Copy link
Contributor

@oZakari oZakari left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See above

@oZakari oZakari added the Enhancement New feature or request label Oct 20, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants