Daniel Swarbrick

@ThomasWattez If I apply the time interval definition that you originally described, it loads without error, but it's obvious what the problem is. The relevant output from `amtool config show`:...

By extension, your second example will specify three logical-or criteria, and also definitely won't do what you expect: ```yaml - name: offhours time_intervals: - times: #

You're most welcome. I'm glad it's now working as you intended.

I don't believe the routing tree editor has any concept of time intervals, since there is no way to supply the time at which you want it to simulate the...

Alertmanager is working as intended. If a route's `active_time_intervals` do not match, that route will not be active - neither to send a "firing" notification, nor to send a "resolved"...

Generally this type of thing is better configured in your notification provider, e.g. PagerDuty, OpsGenie etc, since that's where you configure your teams, on-call schedules, escalation rules etc. Just let...

This test fails pretty regularly during autopkgtest in the prometheus-alertmanager Debian package also. It _seems_ to be less reliable on non-amd64 archs. Also, what strikes me as curious is how...

Any chance of resurrecting this PR? Using the standard library `embed` would make Alertmanager quite a bit simpler to package in Debian, where `shurcooL/vfsgen` is not packaged.

This can already be accomplished with process-exporter: https://github.com/ncabatoff/process-exporter#open_filedesc-gauge

@shaohk Are you implying that you suspect the contents of `/proc/netstat` are changing mid-flight when procfs reads that file? I would be skeptical of that, since it is read with...