Sergey

@roidelapluie One way I see as a solution is splitting `expr` into two fields, one would be the metric itself without any thresholds, and the other would be a threshold...

@beorn7 agree, one of the options to get over it would be to make the older approach work, and add a new one (with two separate fields). do you think...

I have a usecase for it: I maintain a public repo with my ansible playbooks. I want to share some jobs, but keep others private, so it'd be extra handy...

That would solve it for me. Any estimation on when this can be merged?

Just noticed it basically duplicates #734, but with more context.

Might be the same issue: https://github.com/informalsystems/hermes/issues/3547

@adizere I guess ``` Apr 02 23:46:59 monitoring-logging hermes[634298]: 2024-04-02T21:46:59.002990Z WARN ThreadId(25) worker.batch{chain=cosmoshub-4}:supervisor.handle_batch{chain=cosmoshub-4}:supervisor.process_batch{chain=cosmoshub-4}:worker.packet.cmd{src_chain=cosmoshub-4 src_port=transfer src_channel=channel-141 dst_chain=osmosis-1}:relay{odata=35f843ed ->Destination @4-19830002; len=1}:send_messages_and_wait_check_tx{chain=osmosis-1 tracking_id=35f843ed}:send_tx_with_account_sequence_retry{chain=osmosis-1 account.sequence=6071}:estimate_gas: failed to simulate tx, falling back on default gas...

@roidelapluie which Prometheus version should we expect this at? or was it released already?

Is this issue being worked at right now? I am facing this issue as well: my fullnode returns some signing infos with empty `address`, so I cannot map it to...

I faced this yesterday on Neutron emergency upgrade on 2 nodes. Might be because I used --force flag as there was already an upgrade-info.json file there. @julienrbrt can we get...