Uh oh!
There was an error while loading. Please reload this page.
feat: operator liveness metric - #1621
Conversation
uri-99
commented
Dec 16, 2024
WIP discussing the possibility of a graph |
Oppen
commented
Dec 17, 2024
Given we need the metric, wouldn't it be better to merge and change later to improve its display? |
avilagaston9
commented
Dec 17, 2024
I agree with this. I don't know how much information an historical graph will add. |
Oppen
commented
Dec 18, 2024
avilagaston9
commented
Dec 18, 2024
I was missing the step to send proofs, but from the picture you send it looks like you are already doing that. I followed the steps again an it worked in my machine 🤔.
Yes, the metric is configured to show only the missed responses in the selected time range on the top-right corner: |
Oppen
left a comment
There was a problem hiding this comment.
Worked after solving the skill issue shortening ttl for tasks.
JuArce
left a comment
There was a problem hiding this comment.
- Remove the "total" transformation in grafana dashboard
- Sort the values by higher not responding operators first
avilagaston9
commented
Dec 23, 2024
I added the total transformation since when only one operator was missing tasks, no name was displayed on the bar gauge: ![]() Also, the bar gauge lacked an option to dynamically order the labels. I addressed both in #15a53ae by switching from a "Bar Gauge" to a simple "table + gauge display" with successful results: ![]() |






Operator Liveness Metric
Motivation
We need a way to rapidly determine if an operator is down.
Description
Adds a Bar Gauge with the count of missed tasks for each operator over a specified time range.
How To Test
missing_operatormethod from the telemetry terminal with the initialized operator names:localhost:3000and you should see the dashboard with the values.Test also the full flow:
config-files/config-aggregator.yamland reduce thebls_service_task_timeout.Type of change
Checklist
testnet, everything else tostaging