No, that expression would give you the number of seconds since the start of
the last scrape of a target (or recording rule evaluation), relative to the
query evaluation timestamp.
For example, if you had a scrape interval of 15s, that value would move
somewhere roughly between 0s - 15s. See:
Given the benchmarks it seems like moving away from gogo is not feasible
with the current protobuf schema.
I've only now looked at the remote write 2.0 branch, and that might fix the
issues with label allocations.
Any reason samples are still encoded as a list of pairs? Using two arrays
would
2 matches
Mail list logo
