Craig Ringer
Could this be done by continuing to (ab)use the info-metric pattern, storing the string-value data in a label? Then defend against the impact on the inverted TSDB indexes by supporting...
> The most useful string data I can think of are things which do not change often, like a version number These are reasonably handled by the info-metrics convention already....
@rdiez > You may be right. I am no Prometheus expert, but perhaps you can tell me how to implement these from the list above: > > * I want...
Off the top of my head useful values would include: * successful rotation count (counter) * last rotation timestamp (gauge, unix epoch timestamp) * is `cmd` running (gauge, bool) *...
It can't seem to cope with traps like ``` function premature_exit() { echo 1>&2 "Unexpected premature exit from entrypoint script at $0:$line" } trap 'line=${BASH_LINENO:-};premature_exit' EXIT # ... do work...
sidecar: Greatly increased Thanos sidecar memory usage from 0.32.2 to 0.32.3, still exists in 0.35.0
Is it potentially possible to do a tapesort or similar with tempfiles on disk for larger datasets? Since this change I'm finding that queries that run fine on Prometheus directly...
sidecar: Greatly increased Thanos sidecar memory usage from 0.32.2 to 0.32.3, still exists in 0.35.0
Won't it need to spool/buffer then, since it can't recall output it already sent onwards to the downstream? Once it detects the unsorted output it's too late to recall the...
Good point @kfox1111 , since `exec` re-uses the pid that'd work. Sensible workaround. For others, here's what they suggested doing: ``` #!/bin/bash set -e -u # spiffe_helper.hcl also contains "pid_file_name=mycmd.pid"...
https://github.com/spiffe/spiffe-helper/pull/252 proposes to fix this, once the dependent PRs are merged and I can rebase it
@kfox1111 Using the modified script with a subshell will avoid the need for retrying signal delivery, yes. It's not exactly user friendly and most users will probably just have race-prone...