I have created an alert for the blob storage and it start sending emails so frequent. When I’m trying to delete the alert and not able to find the alert in the list but the alert emails are still coming.
I need to know why this alert email is coming or resolve this issue and need to delete / disable this alert
According to your description, I assumed that you could leverage Azure Resource Explorer to manage your alert rules. You could follow the steps below to achieve this purpose.
Log in to Azure Resource Explorer
Input the keyword alertrules into the search box from the top and select the alert rule you created before.
You could disable your alert rule by clicking Edit button, then set isEnabled to false, then click Put button.
Note: You need to switch to "Read/Write" mode from the top to do this operation.
Also, you could click the tab "Actions(POST, DELETE)" in the above screenshot, then click Delete button to delete your alert rule.
Related
I created alert rule in log analytics,and then i exported template to create another alert rule automatically
I need to create alert rule automatically exactly same as manually created alert rule
I am able to create alert rule with the exported template,but the alert rule condition which is created by template is different from alert rule which is created manually in the portal
as shown in below diagrams:
Let me know if any additional information required
Thanks in advance
The screenshots in your question are of the alert Condition names, Azure derives these from the properties of the alert condition. The Condition names can't be set explicitly when creating an alert in the Azure Portal or via an ARM template. Unfortunately it seems that Azure Resource Manager produces slightly inconsistent Condition names depending on whether the alert is created in the Azure Portal or via an ARM template.
As long as the ARM template wasn't modified you should see that the alert condition properties are the same, you can inspect these by clicking on the Whenever the average custom log search is greater than or equal to 1 or Whenever the Count of the Custom log search is greater than or equal to 1 links, that should bring up the Configure signal logic blade.
Issue: The "Pricing Tier" dropdown is empty due to which the create Translator resource workflow fails as the form validation is unsuccessful.
Background: I am trying Azure for the first time so I have free credit and free testing for 30 days on this account.
What I have tried:
I went to create resource and selected "Translator"
I clicked create and then filled in the details but the Pricing Tier dropdown is empty, so I could not select anything:
Next, I clicked on "Review and Create" but it does not create as validation failed:
Now, I am stuck and don't know how to go forward. Appreciate any help that I can get.
This is a bug on our end and we are working to fix it. Meanwhile, as a workaround, can you try changing between subscriptions/regions and the pricing tier should load.
I would like to set up an Azure alert for when someone on our team sets up an Azure database. Once alerted, I want to have an additional alert created if that resource is running for more than a certain amount of time.
My solution is to create an Alert Rule on the storage account and have it send an email. Where I'm running into trouble is how to monitor the database, since it just got created and I don't know the name yet for the second Alert rule that will monitor its uptime.
Is there some programmatic way to determine the database resource name?
If you don't want to invest time in Programmatic way there is a option to set or configure an alert at Resource Group level based on Resource type, where in the alert rule configure with below configurations
Scope -Select the right subscription, filter by resource type like SqlDatabase and if required filter based on location wise
Condition - In Select condition, Signal type drop down select "Create/Update Azure Sql Database" and in alert logic you can provide additional filtering logic's
Can choose existing Action group or create new one based on your requirement
Add "Alert rule details" like rule name, description etc.
Finally create alert rule
Now once alert rule is created if any new Azure SqlDatabase is created you will be notified based on alert configured.
According to the official doc, you can use Event Grid to notify Azure Automation when a SQL database is created.
https://learn.microsoft.com/en-au/azure/event-grid/overview#ops-automation
Once you subscribe, you can use Logic Apps to send you an email for example.
About the second part, you'll need to query the metrics and figure out if it's running (is performing compute) or not.
I'm new to Azure platform. I'm trying free trial and creating a CI/CD setup for docker by following from the below link.
https://www.azuredevopslabs.com/labs/vstsextend/docker/
I have no issue until setting up build definition. I'm getting below issues when doing changes in the release definition.
when i click on "Authorize" button in azure subscription, I'm getting below issue.
Please let me know what mistake i am doing.
well, the text says it all. you are trying to create a connection with a name that already exists. you need to call it something different or rename the existing one
I have created a new service connection and mapped in the release definition.
Click on Manage link
Click on New service connection button
at top right corner
Select Azure resource manager
Once you select the respective option and click Next. Enter valid name and select respective subscription and resource group details.
When I try to create a new Azure Redis Cache and choose a location I just get a "There are no locations available." message.1 Setting everything else first still results in the same error. Refreshing the page doesn't resolve the issue. The problem occurs in both IE and Chrome.
Thanks for reporting this. It seems to be a bug in the portal. I can reproduce it if I click "Location" immediately after the "New Redis Cache" blade opens. However, if I wait a few seconds before clicking "Location", it doesn't repro.
As a workaround, if you close and reopen the "Location" blade it should populate correctly.
We will also work on fixing this in the portal.
Finally, for any issues with Azure Redis Cache you can contact us via email at azurecache#microsoft.com.
After working with the Azure team via email we were able to narrow down the problem and find a workaround.
There are 3 problems at work here that result in my symptoms:
The various New blades in the portal will default you to a disabled subscription. I believe they currently default to the first subscription (oldest) which may not be an active subscription. This results in the default behavior upon choosing a blade to be that of no-subscription.
The New Redis Cache blade will only show locations if you have selected a valid (not disabled) subscription. This behavior differs from the other New blades (such as Create VM) which will show you locations even if you have a disabled subscription selected.
Changing the resource group will automatically change the subscription and lock it, but changing the subscription in this way will not trigger an update to the blade. This means that the locations don't get updated for the new subscription because the subscription-changed-event (made up name) was not fired. In my case, I was always changing the subscription by way of changing the resource group, so I was never able to set the location.
The workaround:
Simply change to an active subscription before choosing a resource group. This will cause the locations list to be updated, and you can then choose a resource group after.