Ignas Kaziukėnas

Any plans to release this soon? It's very annoying that this produces a lot of warnings in projects that use this library.

I got some more logs from alertmanager: ``` DEFAULT 2024-02-01T16:32:45.924029764Z [resource.labels.podName: vmalertmanager-vmalertmanager-1] [resource.labels.containerName: alertmanager] ts=2024-02-01T16:32:45.923Z caller=dispatch.go:163 level=debug component=dispatcher msg="Received alert" alert=SomeName[9da5035][active] DEFAULT 2024-02-01T16:32:45.926752976Z [resource.labels.podName: vmalertmanager-vmalertmanager-0] [resource.labels.containerName: alertmanager] ts=2024-02-01T16:32:45.926Z caller=dispatch.go:163 level=debug...

Here's the simplified alert definition: ``` - alert: HighCPUusage debug: true expr: avg_over_time(instance_cpu_average_utilization{instance_id="instanceId"}[5m]) > 0.85 labels: severity: critical ``` `ALERTS{alertname="HighCPUusage"}` returns a consistent line over the target period while `ALERTS_FOR_STATE`...

After a break I got some more information. Our `evaluationInterval` is set at `15s` and `evalDelay` is default at `30s`. Looking at vmalert code it seems that this results in...

> It should be simply ` now()+4*evaluationInterval`. Could you point me to the code where evalDelay is subtracted? Could you please share version of your vmalert? If I'm reading things...

> Do you consider updating to newer version of vmalert with the fix included? I see the operator helm chart was updated today. So definitely will try to upgrade sometime...

The `endsAt` are now greater than it was before. Another thing that has also changed is that it's no longer rounded to the next `evaluationInterval` but I guess it's not...

Yes. Something along these lines.

After further investigation it seems like on install the Oncall plugin fails to read org and user data and then all further calls fail because of this as it has...

> Also ran into this, on provider version `5.45.0` and terraform version `1.7.0` I managed to work around it with this patch: > > ```terraform > security_and_analysis { > secret_scanning_push_protection...