Issues with _Asim_, Im and _Im_ due to basic log table being present/created in Sentinel LAW
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- observability
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.
Description
- Dominant language
- PowerShell
- Stars
- 1.2k
- Forks
- 493
- PR merge metrics
- No merged PRs in 30d
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.
More from microsoft/AzureMonitorCommunity
-
Difficulty 3/5 1-2 days Newbie friendliness 58/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 10/100
All issues in microsoft/AzureMonitorCommunity
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
backend bug tracing
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
future-agi/future-agi#3022 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
traceloop/openllmetry#4502 ·
-
area/distributed-query area/observability kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100