Three new connectors this month, covering very different ground: remote site connectivity with Zscaler Zero Trust Branch, backup with Veeam Backup & Replication 13, and dependency on third-party SaaS services with Atlassian Statuspage.
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
- 7 enhancements to existing connectors
- 5 fixes to existing connectors
New Monitoring Connector Highlights
[New connector] Zscaler Zero Trust Branch REST API
Why it matters
Zero Trust Branch is Zscaler’s offering for connecting remote sites: gateways (Branch Connector) deployed at branch offices redirect traffic to the Zscaler cloud, replacing site-to-site VPNs. When a site’s traffic depends on this gateway, a degraded gateway, an unstable WAN interface or a downed IPsec tunnel to Zscaler Internet Access cuts off access for the site. This connector queries the ZTB API (OAuth2 authentication) to track gateway health, their resources and the quality of their WAN links: jitter, loss, latency and score.
Typical use case
You have deployed ZTB gateways across several branch offices and want to spot a WAN link degradation or an inactive IPsec tunnel before users report it. Auto-discovery creates the hosts in Centreon that correspond to the gateways and clusters. A cache mode reduces the number of API calls when several gateways are monitored (see the documentation page for more information).
Monitored modes
gateway-status · gateway-cpu · gateway-memory · gateway-disk · gateway-interfaces · gateway-containers · cluster-ipsec · cluster-appconnector · discovery · cache
[New connector] Atlassian Statuspage
Why it matters
Many SaaS vendors publish the status of their services on an Atlassian Statuspage page. Each page exposes a public JSON endpoint, with no authentication required, that lists every component along with its status. This connector reads that endpoint.
Typical use case
One of your applications depends on a third-party service (API, payments, video…). When users report a problem, you can see directly in Centreon whether the provider has declared an incident on the affected component. Components can be filtered by name or by group, and service discovery creates one service per component.
Monitored modes
components
[New connector] Veeam Backup & Replication REST API
Why it matters
Since version 13, Veeam Backup & Replication is also distributed as a Linux appliance. On this type of deployment, the existing Centreon connectors, which rely on PowerShell on a Windows server (via CMA, NSClient, NRPE or WinRM) or on Veeam Backup Enterprise Manager, cannot be used. This new connector queries the VBR server’s REST API directly (port 9419 by default, OAuth2 authentication), with no intermediate agent. The need was raised through a highly voted idea on The Watch.
Typical use case
You are migrating or deploying your backup servers on VBR 13 and want to keep visibility on your backups in Centreon:
- the status and last result of each job;
- the available space on repositories;
- license consumption and expiration;
- the availability of servers managed by Veeam (vCenter, Hyper-V, Windows or Linux hosts).
Monitored modes
jobs · licenses · managed-servers · repositories
Monitoring Connector Update Summary
New Monitoring Connectors
Enhancements
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!