printf query on resolved alert not showing current state

[ojle]

I have following alert rule:

groups:
- name: loadavg
  rules:
  - alert: HighLoadAvg
    expr: ((system_load5 / count without (cpu, mode) (cpu_usage_idle{cpu!="cpu-total"})) > 1.3)
    for: 2m
    labels:
      severity: warning
    annotations:
      description : 'load average: {{ printf `system_load1{instance="%s"}` $labels.instance | query | first | value }}, {{ printf `system_load5{instance="%s"}` $labels.instance | query | first | value }}, {{ printf `system_load15{instance="%s"}` $labels.instance | query | first | value }}'

When triggered I get in email current load stats:
WARNING - load average: 4.16, 3.54, 2.25
When resolved I also get current load stats:
OK - load average: 1.19, 2.64, 2.79

If I try similar rule for disk space, ie.

description : 'disk space: {{ $labels.path }} {{ printf `disk_used_percent{path="/tmp",server="%s"}` $labels.server | query | first | value | humanize }}%'

I only get current stat when alert is triggered, ie.
WARNING - disk space: /tmp 82.72%
and then
OK - disk space: /tmp 82.72%

Am I missing something here?
How/why is the query on resolved alert for system_load being evaluated?

running prometheus 2.0.0

[brian-brazil]

I see nothing odd here, a 1 or 2 core machine can produce such output.

[ojle]

But with disk_space alert, once it was resolved, I was suppose to get current value as I did with load average.
So instead of:
OK - disk space: /tmp 82.72%
I should get:
OK - disk space: /tmp 40%

To be clear, load average alert when resolved gave current server load state with
{{ printf `system_load1{instance="%s"}` $labels.instance | query | first | value }} ....
and disk free alert once resolved it didn't gave disk current state with
{{ printf `disk_used_percent{path="/tmp",server="%s"}` $labels.server | query | first | value | humanize }}%'

[brian-brazil]

Resolved alerts do not have annotations set, you are misinterpreting what's going on.

[ojle]

Ok, then do you have valid explanation what is going on here?
If it is as you are saying, then when the alert triggered with message:
WARNING - load average: 4.16, 3.54, 2.25
once was resolved, I was suppose to get:
OK - load average: 4.16, 3.54, 2.25
right?

And instead I got:
OK - load average: 1.19, 2.64, 2.79

[brian-brazil]

Another evaluation of the alert updated the annotations.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.