A new version of check_rancher2, a monitoring plugin to monitor Kubernetes clusters managed by Rancher2, is available!
Version 1.2.3 contains a fix which now handles HTTP 403 errors from the Rancher2 API correctly. Prior to that, the plugin simply returned json read errors but exited with status OK:
# ./check_rancher2.sh -H rancher.example.com -S -U token-xxxxx -P secret -t info
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
json read error: line 1 column 1: '[' or '{' expected near '<'
CHECK_RANCHER2 OK - Found 0 clusters: and 0 projects: |'clusters'=0;;;; 'projects'=0;;;;
The plugin now correctly identifies and alerts when access to the API is forbidden:
# ./check_rancher2.sh -H rancher.example.com -S -U token-xxxxx -P secret -t info
CHECK_RANCHER2 CRITICAL - Access to API forbidden
No comments yet.
AWS Android Ansible Apache Apple Atlassian BSD Backup Bash Bluecoat CMS Chef Cloud Coding Consul Containers CouchDB DB DNS Database Databases Docker ELK Elasticsearch Filebeat FreeBSD Galera Git GlusterFS Grafana Graphics HAProxy HTML Hacks Hardware Icinga Influx Internet Java KVM Kibana Kodi Kubernetes LVM LXC Linux Logstash Mac Macintosh Mail MariaDB Minio MongoDB Monitoring Multimedia MySQL NFS Nagios Network Nginx OSSEC OTRS Office PGSQL PHP Perl Personal PostgreSQL Postgres PowerDNS Proxmox Proxy Python Rancher Rant Redis Roundcube SSL Samba Seafile Security Shell SmartOS Solaris Surveillance Systemd TLS Tomcat Ubuntu Unix VMWare VMware Varnish Virtualization Windows Wireless Wordpress Wyse ZFS Zoneminder