microsoft / microsoft/AzureMonitorCommunity
Issues with _Asim_, Im and _Im_ due to basic log table being present/created in Sentinel LAW
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
Description
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 by reviewing the three attached screenshots and reproducing the behavior in an Azure Sentinel Log Analytics Workspace. The issue does not identify a file, query, test, or expected correction; clarify the impact involving Asim, Im, and Im before defining what done means.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100