-
Bug
-
Resolution: Done
-
Normal
-
Logging 5.7.0
-
False
-
None
-
False
-
NEW
-
VERIFIED
-
Before this update, the log_forwarder_output metric did not include http. This update adds the missing parameter to the metric.
-
Bug Fix
-
-
-
Log Collection - Sprint 235, Log Collection - Sprint 236
Description of problem:
similar to https://issues.redhat.com/browse/LOG-3932, http need to added into log_forwarder_output_info.
Steps to Reproduce:
1)deploy openshift-logging.
2)Check the log_forwarder_output_info
token=$(oc create token prometheus-k8s -n openshift-monitoring)
pod=$(oc get pods -o name |head -1)
route=$(oc get route -n openshift-monitoring prometheus-k8s -ojsonpath={.spec.host})
oc exec $pod – curl -k -s -H "Authorization: Bearer $token" "https://${route}/api/v1/query?" --data-urlencode "query=log_forwarder_output_info" | jq '.data.result'
Actual results:
{ "metric": { "__name__": "log_forwarder_output_info", "cloudwatch": "0", "default": "0", "elasticsearch": "0", "endpoint": "http-metrics", "fluentdForward": "0", "kafka": "0", "loki": "0", "syslog": "0" "http": "0", "namespace": "openshift-logging", .... .... }, }
Expected results:
{
"metric":
,
}
- is cloned by
-
LOG-4174 [release-5.8] Add http to log_forwarder_output_info metrics
- Closed
- is related to
-
LOG-3932 No log_forwarder_output_info for splunk and google logging
- Closed
-
LOG-4098 [release-5.7] No log_forwarder_output_info for splunk and google logging
- Closed
- links to
- mentioned on