Centreon Monitoring Agent vs Telegra

When Centreon wanted to be compatible with OpenTelemetry, we started with an existing agent: Telegraf.

Now we have developed our own agent, allowing in addition to locally executing plugins and native checks, in order to be able to completely replace the NSClient++ agent with Centreon Monitoring Agent.

Hi, thanks for your interest in Centreon Monitoring Agent.

In order to complete what ​@Laurent explained, Centreon Monitoring Agent has the following advantages :

• Improved performance/network footprint in host-poller communication
• Improved default security (tokens and TLS)
• Offline plugin installation (Windows)
• Simplified configuration on Windows host (no configuration files to modify, directly done by Installer/CLI)
• Monitoring configuration updated without action on the host (agent reloading required with Telegraf for each configuration update)
• Connection Poller → Agent, to meet security requirements prohibiting outgoing flows (e.g. DMZ)
• Outputs in monitoring data
• Centreon support and dedicated roadmap

Let me know if you have any additional question

Regards,

That’s for Microsoft Windows.

What about GNU/Linux ?

There is a version for Windows and a version for Linux systems, the install procedure is on their plugin docs Centreon Monitoring Agent | Centreon Documentation

hello

Thank you for your reply.
So can we assume that Agent Telegraf will disappear?

Philippe

We aim to make Centreon more OTLP compliant, including ability to receive metrics from any OTLP Collector/Exporter, so Telegraf Agent will remain supported as it is, and this support may evolve towards observability (undeclared metrics) in the future.