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.yaml with alert rules for at minimum DroppedPackets and SNATConnectionCount
- Add the new file to the
_create_alert_configmap list in grafana_alloy.py
- Add test coverage in
test_azure_alert_files.py
Azure NAT Gateway metrics (DroppedPackets, SNATConnectionCount, etc.) are currently scraped via
prometheus.exporter.azurein Grafana Alloy whenpublic_subnet_cidris configured, but there are no corresponding Grafana alert rules for these metrics.The existing
natgateway.yamlcovers AWS CloudWatch only. Azure NAT Gateway metrics have no alert coverage yet.Metrics currently scraped:
PacketCountByteCountDroppedPacketsTotalConnectionCountSNATConnectionCountAcceptance criteria:
azure_natgateway.yamlwith alert rules for at minimumDroppedPacketsandSNATConnectionCount_create_alert_configmaplist ingrafana_alloy.pytest_azure_alert_files.py