20e93cea4c97696cdceaefb8a142c5ebc8a213d5
Found during live testing: netdata's cloud-provider auto-detection runs curl --fail -s -m1 --noproxy * http://169.254.169.254 on every startup/reconnect to check whether the host is in AWS/GCP/Azure - standard monitoring-agent behavior, not a bug. Without this exception the rule would have paged every time netdata restarts. Scoped to netdata's own curl specifically so any other connection from that container still alerts.
docker-infrastructure
Languages
Shell
58.2%
Python
28%
JavaScript
10.5%
HTML
2.3%
DIGITAL Command Language
0.6%
Other
0.4%