The Palo Alto API connector moves beyond the single-firewall scope: it now automatically discovers managed devices through Panorama, along with health and certificate tracking. On 3CX, an upgrade to version 20 broke compatibility with the connector, fixed with the help of a user who tested the patch on his own Enterprise and Pro environments.
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
- 79 enhancements to existing connectors
- 2 community contributions (Github & The Watch)
- 11 fixes to existing connectors
New Monitoring Connector Highlights
Major enhancement – Palo Alto API: Panorama support
Why it matters: The Palo Alto API connector used to be limited to individual firewalls. It now adds automatic discovery of firewalls managed through Panorama, along with health and certificate modes available on both the firewall and Panorama itself. Organizations running their firewall fleet from a central Panorama can now have devices discovered automatically instead of adding them one by one.
Typical use case: You manage several Palo Alto firewalls through a central Panorama and want Centreon to automatically discover the managed firewalls, with health status and certificate tracking.
Monitored modes: discovery, health, certificate, licenses, system, environment, ha, ipsec
Dynamics 365 CMA and EMC Symmetrix CMA: continuing the move to the CMA agent
These two new packs continue the migration of Windows application connectors historically based on NSClient++ (via NRPE) to the CMA agent, a move already started in previous releases. Monitoring coverage stays the same as the existing NRPE packs (same host and service templates) only the collection method changes, with an agent that’s simpler to deploy and maintain than NSClient++.
Community trends
New connector – Waystream Standard SNMP
Roman Morandell from iVertix contributed this connector for Waystream network devices, switches and routers used notably in industrial and transportation environments. Coverage is broad: CPU (overall and detailed usage), memory, network interfaces, SFP ports, hardware status (temperature, voltage), ARP tables, TCP/UDP connections, and uptime — enough to track both the health of the device and the network activity flowing through it, without combining several connectors.
PR #5956 https://github.com/centreon/centreon-plugins/pull/5956
Compatibility- Apps-VoIP-3CX-Restapi: 3CX v20 compatibility
Why it matters: 3CX significantly changed its API with version 20, notably renaming several endpoints (and last year, some v18 endpoints were still unavailable). As a result, the existing connector stopped working for any instance upgraded to v20. The connector update to support v20 was proposed and tested directly by a user, Jean-François EGEA, on his own 3CX Enterprise and Pro environments (adding a license mode along the way), before being taken as a contribution.
Typical use case: You’re monitoring a 3CX system upgraded to version 20 (Enterprise or Pro) and your connector has stopped returning data since your PBX update.
Monitored modes : system, extension, license
July Monitoring Connector Update Summary
New Monitoring Connectors
Enhancements
There are also a lot of SNMP connectors for which native SNMP v3 macros have been added.
Furthermore, for most of the AWS and Azure connectors, the host status check has been modified to better reflect, where possible, the actual health status of these hosts.
Bug fixes
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
