Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides troubleshooting guidance for Azure Monitor issues and investigations. The article explains the causes of these problems and offers steps to address them. It also includes links to related Azure Monitor documentation for further reference.
Lack of permissions to run observability agent investigations
You must have the Issue Contributor, Monitoring Contributor, or Contributor role assigned for the target resource.
If you don't have permission, you can't create an issue or run an observability agent investigation, and you should consult with your system administrator.
Lack of associated Azure Monitor Workspace (AMW)
You must have an AMW associated to the subscription you're investigating. To create the association, consult with your system administrator. See Associate an Azure Monitor Workspace with a subscription.
No findings
When an observability agent investigation is run, you might receive a No findings result. This result isn't a problem – it just means the observability agent didn't detect any anomalies in the metrics, logs, or other monitored data. It's important to remember that this result doesn't necessarily indicate the absence of underlying issues, but rather that the current data doesn't reveal any obvious problems.
OpenAI issue
The observability agent depends on OpenAI for the text generation to function correctly. Occasionally, OpenAI might experience problems. If you encounter a screen indicating a problem with OpenAI, try refreshing the page and running the observability agent investigation again from the beginning. In the meantime, you can still review the anomalies detected without the summary, which can help identify potential issues even if the summary functionality is unavailable.