-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
None
Description of problem:
There is an offset in the measure in the rhods_aggregated_availability metric of a couple of seconds that makes the measure unreliable. This offset seems to be due to the traefik component, so it has to be solved when kubeflow will be implemented. This issue is a track from the issue RHODS-4358
Prerequisites (if any, like setup, operators/versions):
Install Rhods
Steps to Reproduce
- Go to Prometheus
- Write the query rhods_aggregated_availability
- Execute the query several times until you see the offset
Actual results:
There is an offset in the measure
Expected results:
The measure is the same every time you perform the query
Reproducibility (Always/Intermittent/Only Once):
Always
Build Details:
Workaround:
Additional info:
- is related to
-
RHODS-4229 Update rhods_aggregate_availability metric to include a label for individual components
- Closed
-
RHODS-4358 Glitch in rhods_aggregated_availability due to probe_success metrics
- Closed
- relates to
-
RHODS-4358 Glitch in rhods_aggregated_availability due to probe_success metrics
- Closed