Skip to content
This repository has been archived by the owner on May 3, 2023. It is now read-only.

check_openshift_node_log_heartbeat not working with oc 3.11 #64

Open
ghost opened this issue Dec 10, 2019 · 1 comment
Open

check_openshift_node_log_heartbeat not working with oc 3.11 #64

ghost opened this issue Dec 10, 2019 · 1 comment
Assignees

Comments

@ghost
Copy link

ghost commented Dec 10, 2019

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

Thanks

@megian megian self-assigned this Dec 18, 2019
@megian
Copy link
Collaborator

megian commented Dec 18, 2019

We are currently using an older oc binary with the plugin, because we still have older clusters than 3.11 to monitor. Since we are working on a tool passing Prometheus Alertmanager events to Icinga, the Nagios plugin is currently not in our focus.

It is planned that we are OpenSource this tool too, but there is no ETA yet. So meanwhile you also might use an older oc binary with the the check.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant