search

sanchitmehta / azure-container-apps-issues-test

0 stars 0 forks source link

Log Analytics not working #9

Open sanchitmehta opened 1 year ago

sanchitmehta commented 1 year ago

Log Analytics not working

bugdestroyer3000[bot] commented 1 year ago

Hello,

Thank you for bringing this to our attention. We understand that you're encountering an issue with Log Analytics not working.

Based on the details you've provided, we've classified this as a Observability, Bug Report issue.

Here's a potential way to address the issue, based on our current understanding:

Based on the information provided, it seems that the issue is related to Log Analytics not working in Azure Container Apps. One possible solution is to utilize the Kusto query mentioned in the relevant documentation to display console log entries for the specific named app. This could help identify any errors or issues that may be preventing Log Analytics from working properly. Additionally, it may be helpful to review any relevant logs or error messages to further diagnose the issue. If the issue persists, it may be necessary to reach out to Azure Support for further assistance.

For more information, you might find these documents helpful: Source: [publicDocs] Summary: { "Summary": "This article provides information about monitoring logs in Azure Container Apps with Azure Monitor Log Analytics. It explains the two types of logs available: Console logs and System logs. Additionally, it mentions the Kusto query that displays console log entries for a specific named app, which could be useful in troubleshooting the issue related to Log Analytics not working." }

Source: [githubIssues] Summary: { "Summary": "The two documents are related to issues users are experiencing when trying to start Docker Desktop on different versions of Windows. The first document refers to a specific update on Windows 10 21H1, which causes the application to fail to start without any error message. The second document describes a similar issue on Windows 10 20H2. The concise summaries provide a brief description of the issue, and the response from Docker confirms that they are investigating and will provide an update soon." }

We appreciate your patience and understanding as we work to resolve this. We've forwarded this issue to our developers and initiated an investigation. We'll keep you updated on the progress.

In the meantime, if you have any other questions, or if there's anything else you need help with, please don't hesitate to ask.

Best regards, BugVaporizer3000