Add azure_natgateway.yaml alert rules for Azure NAT Gateway metrics
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
Azure NAT Gateway metrics (DroppedPackets, SNATConnectionCount, etc.) are currently scraped via prometheus.exporter.azure in Grafana Alloy when public_subnet_cidr is configured, but there are no corresponding Grafana alert rules for these metrics.
The existing natgateway.yaml covers AWS CloudWatch only. Azure NAT Gateway metrics have no alert coverage yet.
Metrics currently scraped:
PacketCountByteCountDroppedPacketsTotalConnectionCountSNATConnectionCount
Acceptance criteria:
- Create
azure_natgateway.yamlwith alert rules for at minimumDroppedPacketsandSNATConnectionCount - Add the new file to the
_create_alert_configmaplist ingrafana_alloy.py - Add test coverage in
test_azure_alert_files.py
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 existing natgateway.yaml alert rules and the _create_alert_configmap list in grafana_alloy.py. Create azure_natgateway.yaml with rules for at least DroppedPackets and SNATConnectionCount, then add coverage in test_azure_alert_files.py. Done means the new alert file is included in the config map and its tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100