Copolycube
Copolycube
Hello @GregYankovoy I submitted the https://github.com/GregYankovoy/docker-goaccess/pull/16 that contains this feature (among others).
Ok, thanks for the explanation. I was looking at the PromQL functions and hadn't find anything relevant indeed :-( Ideally I'm hoping to make the dashboards and alerts only rely...
@dswarbrick you need a paid subscription to be able to publish there
Hello @dswarbrick , with `sum by(job) (apt_upgrades_pending{origin=~".*Security.*"}) or vector(0)` you only get `{} 0` as a global result when there are no match / no security upgrades on each instance....
Hello, I just witnessed exactly the same logs after upgrading my mainnet and granadanet octez tezos nodes (docker images) from `tezos/tezos:v9.7` to `tezos/tezos:v10.0` . ``` $ sudo docker-compose logs --tail=50...
I just tried the suggestion from error #23 and the RPC mentionned there is answering correctly in my case (my node's RPC is on 8733) ``` $ curl -s -D...
Insecure workaround is still required.
@kllp if it helps there is also a copy of my configuration here : https://gist.github.com/copolycube/dc6a52812fea19361f5aa5b0f3d514dd
Hello, depending on your goal here : it might be easier for you to limit the "exporter part" to what you want to monitor _live_ (i.e. what you want to...
Hello, thanks @danielelisi for your answer. if that was the case then the error would be the same on mainnet, no ? as you can see here : https://gitlab.com/nomadic-labs/umami-wallet/umami-stack-orchestration/-/blob/main/umami-stack-compose/docker-compose.yml#L19 the...