Three new connectors this June, including one for Centreon Log Management, in line with the product launch earlier this month. Also a new OpenShift connector that extends Kubernetes coverage. This month also marks the start of a cross-cutting effort to update SNMP connectors: SNMPv3 macros are now natively available in host templates, removing the need to use SNMPEXTRAOPTIONS. Worth noting as well: a breaking change on NRPE packs replacing the unmaintained check_centreon_nrpe3 with check_nrpe, improving consistency across NRPE packs.
You may also read the related documentation, contact our sales team, or post a message on The Watch to learn more.
Monitoring connector updates by the Numbers
- 3 new connectors added to the catalog
- 46 enhancements to existing connectors
- 2 community contributions (Github & The Watch)
- 10 fixes to existing connectors
New Monitoring Connector Highlights
New Connector Centreon Log Management REST API
Why it matters: Centreon Log Management (CLM) is Centreon’s SaaS log management solution. This connector enables alerts triggered by CLM on your logs to be forwarded to Centreon Infra Monitoring (CIM), alongside infrastructure and user experience alerts. The result is a unified view in CIM via dashboards, the event inbox and application templates. It displays two key metrics: the number of active alerts by severity (unknown, ok, warn, error, critical) and the volume of logs ingested over a configurable period, which is useful for detecting a silent ingestion failure. Further improvements will follow as CLM evolves.
Typical use case: You use CLM to centralize logs from your servers and network equipment. You want to be alerted in CIM if CLM stops receiving logs (ingestion failure) or if a spike in error or critical alerts occurs; without having to check the CLM interface separately. The Log-Count service accepts a custom query to target a specific log stream.
Monitored modes : alert-count, log-count
New Connector OpenShift API
Why it matters: OpenShift is Red Hat’s Kubernetes distribution, widely deployed in enterprise environments. This connector is an extension of the existing Kubernetes connector: it inherits all its services (nodes, pods, deployments…) and adds monitoring of OpenShift-specific objects that native Kubernetes does not cover : ClusterOperators (critical OCP platform components), cluster version, Routes and Projects. Host discovery is included for nodes and namespaces. Access is via the native OpenShift REST API with a Bearer token, with no dependency on oc or kubectl on the poller.
Typical use case: You operate an OpenShift Container Platform 4.x cluster and want to monitor in Centreon the status of platform operators (a degraded or non-upgradeable ClusterOperator blocks OCP updates), the availability of Routes exposed to users, and the overall state of Projects; on top of the standard Kubernetes monitoring already covered.
Monitored modes (OpenShift-specific): clusteroperators, clusterversion, projects, routes
Community trends
Kubernetes API enhancement : allow filtering Deployments using labels
The contributor sylvainrollandmaif noted that the Kubernetes connector’s deployment-status mode did not allow filtering deployments by label, forcing users to monitor all deployments in a cluster. His contribution adds the –include-label and –exclude-label options, making it possible to target only deployments with specific labels. This is useful for segmenting monitoring by team, environment or application in a multi-tenant cluster.
PR #5812 https://github.com/centreon/centreon-plugins/pull/5812
May Monitoring Connector Update Summary
New Monitoring Connectors
Enhancements
Bug fixes
Breaking changes
For more details, check out the full release note.
Want to help or suggest improvements?
- You can submit an idea on The Watch.
- Or contribute on GitHub.
See you next month for more new monitoring connectors!
Share
