Review Frequency for IIS collection rules
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- cloud, observability
Research direction
The issue provides no body, files, tests, or acceptance criteria. Start by clarifying the intended review frequency and which IIS collection rules are affected, then locate those rules in the AzureMonitorStarterPacks repository. Done means the agreed frequency is applied to the identified IIS rules and the result is validated.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- Bicep
- Stars
- 65
- Forks
- 31
- Avg merge
- 3d 11h
- Merged PRs (30d)
- 1
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 Azure/AzureMonitorStarterPacks
-
Difficulty 2/5 1-3 hours Newbie friendliness 38/100
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Azure/AzureMonitorStarterPacks#194 · 3 comments ·
-
Azure/AzureMonitorStarterPacks#165 · 1 assignee ·
-
bug
Azure/AzureMonitorStarterPacks#143 · 1 assignee ·
All issues in Azure/AzureMonitorStarterPacks
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·