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
{{ message }}
This repository was archived by the owner on May 3, 2023. It is now read-only.
Dear,
launching check_openshift_node_log_heartbeat --token-from token --endpoint https://endpoint.xyz nodename
seems not working with OC 3.11 reporting always critical: HEARTBEAT CRITICAL - Node(s) not reporting heartbeat or not contained in query result: nodename | doc_count_error_upper_bound=0 sum_other_doc_count=0;0
Perhaps to do with the fact that the date field in Elastic is not in the format '%Y-%m-%dT%H:%M:%S.%f%z' having unexpected : in time zone, for example: '2019-12-09T15:05:38.647015+00:00'
My Openshift version below
oc version
oc v3.11.0+0cbc58b
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO
Server https://endpoint.xyz
openshift v3.11.135
kubernetes v1.11.0+d4cacc0
Dear,
launching
check_openshift_node_log_heartbeat --token-from token --endpoint https://endpoint.xyz nodenameseems not working with OC 3.11 reporting always critical:
HEARTBEAT CRITICAL - Node(s) not reporting heartbeat or not contained in query result: nodename | doc_count_error_upper_bound=0 sum_other_doc_count=0;0Perhaps to do with the fact that the date field in Elastic is not in the format '%Y-%m-%dT%H:%M:%S.%f%z' having unexpected : in time zone, for example: '
2019-12-09T15:05:38.647015+00:00'My Openshift version below
Thanks