-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.5.0
-
False
-
-
False
-
NEW
-
VERIFIED
-
Logging (Core) - Sprint 218, Logging (Core) - Sprint 219, Logging (Core) - Sprint 220, Log Collection - Sprint 221
The managedStatus is always 1 in metrics log_logging_info no matter whether the clusterloging/instance managedStatus is Managed or Unmanaged.
The healthStatus is always 0 in metrics log_logging_info
the version is 0.0.1. It's better to show CSV version(Logging 5.4.x) or cluster-logging-operator version(1.x)
Note : 0 represents healthy stats, 1 unhealthy status in the description of Log_forwarder_pipeline_info . I think managedStatus and healthStatus should follow the same rules.
Step to reproduced:
1) Check the clusterlogging/instance to Unmanaged.
2) Check the metrics log_logging_info
curl -k -H "Authorization: Bearer $(oc sa get-token prometheus-k8s -n openshift-monitoring)" https://$(oc get route -n openshift-monitoring prometheus-k8s -ojsonpath=
)/api/v1/query?query=log_logging_info
Actual results:
[
{
"metric": {
"__name__": "log_logging_info",
"endpoint": "http-metrics",
"healthStatus": "0",
"instance": "10.130.2.166:8686",
"job": "cluster-logging-operator-metrics",
"managedStatus": "1",
"namespace": "openshift-logging",
"pod": "cluster-logging-operator-b7b7d7f58-v4xsz",
"service": "cluster-logging-operator-metrics",
"version": "0.0.1"
},
"value": [
1648724071.032,
"1"
]
}
]
- links to
- mentioned on