You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my use case, I need to set push_system_cpu_sick_above to 1, but only for one node, to essentially ignore the CPU usage as it is expected that it will be very high. The global value, however, means that whenever my node's replicas do work, they are marked as sick on the next probe due to their high resource usage. I would increase the global value, but there are other nodes that are not expected to have this high resource usage and would be misidentified as healthy if they did.
Essentially, what I'm proposing is an override, similar to this:
# rest of config cut for brevity
[metrics]
push_system_cpu_sick_above = 0.7
[[probe.service.node]]
push_system_cpu_sick_above = 1
The text was updated successfully, but these errors were encountered:
lewisakura
changed the title
Ability to customise metrics.push_* per-node
Ability to customise metrics.push_* per-node
Jul 4, 2023
In my use case, I need to set
push_system_cpu_sick_above
to 1, but only for one node, to essentially ignore the CPU usage as it is expected that it will be very high. The global value, however, means that whenever my node's replicas do work, they are marked as sick on the next probe due to their high resource usage. I would increase the global value, but there are other nodes that are not expected to have this high resource usage and would be misidentified as healthy if they did.Essentially, what I'm proposing is an override, similar to this:
The text was updated successfully, but these errors were encountered: