Cosmos Db Alert triggered when condition not met?
We got a strange issue with our Cosmos Db monitoring alert rule.
We had an alert rule in our Cosmos Db that sends an email to us while serverside latency is above 50ms. The condition setup is as below screenshot.
The intention is to send an email to us when server-side latency is high (in this case greater than 50 ms). However, we received an alert in the morning with no obvious reasons. We received an alert around 7 AM, but when I check the metrics around that time, the highest latency is below 1 ms.
I don't understand how it is possible to trigger the alert rule. Or there is something we are missing in the rule setup?
Any help is much appreciated!
Hi @Zhang, Xiaoliang , welcome to Microsoft Q&A forum.
I would suggest you to raise a support ticket for this as it is really difficult to triage it remotely. Through support ticket, an engineer from MS can work with you and check the real root cause behind it and assist you with the right solution.
Sign in to comment
Hi @Zhang, Xiaoliang , Were you able to raise a support ticket. We need to investigate this issue further in your environment. Please let us know if you run into any issues while creating the support ticket.https://learn.microsoft.com/en-us/azure/azure-portal/supportability/how-to-create-azure-support-request