microsoft / microsoft/AzureMonitorCommunity
Log analytics workspace audit - issues when basic tables exist
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
Hello
When going into a log analytics workspace --> insights it seems that having a single table with Basic tier enabled breaks the entire workbook
It is possible to select specific tables via customize --> edit
But this is a bit of a hassle
e.g.
Would it be possible to extend the workbooks/queries to ignore Basic tier tables by default?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Log Analytics workspace Insights workbook and the workbooks or queries that select tables. Reproduce the failure with a workspace containing a Basic-tier table, then verify that the default Insights view works without manually selecting tables.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, powershell
- Domain
- cloud, observability-sre
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100