Strangeness with `timestamp()` about victoriametrics

[lapo-luchini]

Grafana Explore probably doesn't send step param, so it defaults to 5m when omitted. Does it make sense?

It does! Originally I noticed the problem in vmalert rules, tough, not using vmui.
It had a lot of false negatives in latest updates that didn't happen before.
Might have been a change… but explanation makes sense, I'll add an explicit look-behind window to the rule.

[lapo-luchini]

Seems to be fixed in v1.101.0… ?
(works with Grafana Explore, but the VMUI interface is broken — might be an issue with the fact that I built it myself though, I didn't check in deeper yet)

[hagen1778]

Hello @lapo-luchini!
timestamp function checks for the last timestamp over specified look-behind window timestamp(foo[5m]). If look-behind window is omitted timestamp(foo), then it uses step param instead. On the screenshot you have step 5s, so result is likely depends on whether you had a successful scrape during last 5s + latency_offset (30s), or not.
Grafana Explore probably doesn't send step param, so it defaults to 5m when omitted. Does it make sense?