Azure Portal Log Analytics bug

Question

Found a bug in Azure portal

Answer 1

Hello Gleb , Welcome to MS Q&A

I think more than a bug it seems to me like an incorrect call

You're trying to query a Basic Logs table using the standard query API, which is not supported. For Basic Logs, you must use the /search API instead of /query

Fix

Update your API call to use:

https://api.loganalytics.io/v1/workspaces/{workspaceId}/search

Instead of

https://api.loganalytics.io/v1/workspaces/{workspaceId}/query

Also, make sure your query syntax is compatible with the Basic Logs format.

Pls check and let us know

Thanks
Deepanshu

Answer 2

Hi Gleb,

thanks for sharing this. u're hitting that pesky 'query not supported' error because basic logs tables need a different api endpoint. instead of the usual 'query' one, u gotta use the 'search' endpoint https://aka.ms/basicLogsQueryAPI.

what u can do right now: switch your api call from '.../query' to '.../search'. yes its a small change but it makes all the difference )) if u're using something like powershell or python, just update the url in your code. here's a tiny example if it helps

# old way (won't work)  
# url = 'https://api.loganalytics.io/v1/workspaces/workspaceldi/query'  

# new way for basic logs  
url = 'https://api.loganalytics.io/v1/workspaces/workspaceldi/search'  

as well check this sometimes the workspace id gets mistyped. worth looking into even if u're sure its correct ))

when u see api endpoint errors, always peek at the exact api version and path. this might help in other tools too, not just azure.

oh and if it still acts up after changing the url, that request id (10ec3fbf-975b-4ae5-a605-d9742e04fb2a) is golden. microsoft support can trace everything with it.

basic logs are cheaper but have some limits. u might wanna check if standard logs fit better for heavy query needs. their pricing page has deets https://azure.microsoft.com/pricing/details/monitor/.

keep us posted if u crack it )

Best regards,

Alex

and "yes" if you would follow me at Q&A - personaly thx.
P.S. If my answer help to you, please Accept my answer

https://ctrlaltdel.blog/

Answer 3

To add to the people who have answered without full context, this error in embedded in the Azure Portal.

If you go to an effected Log Analytics Workspace, then go to Monitoring > Insights, you will see all of the graphs are broken. This seems to only be affecting some of my LAWs, but I'm not sure why.

If you click the "expand" the query, you'll get a similar error: