Skip to main content
New

Support for Additional Exporters in Centreon Monitoring Agent

Related products:Infra Monitoring - Centreon Monitoring Agent
  • July 1, 2026
  • 0 replies
  • 3 views

sdouce
Forum|alt.badge.img+12

I would like to propose an enhancement to the Centreon Monitoring Agent (CMA) by introducing support for additional exporters ("extra exporters"), allowing the agent to send collected open telemetry to multiple destinations simultaneously.
 

Introduce an optional extra_exporters section in the CMA configuration.

Example:

{
"endpoint": "centreon.example.com:4317",
"encryption": "full",
"token": "...",
"host": "server01",

"extra_exporters": [
{
"type": "otlp",
"endpoint": "alloy01:4317",
"tls": false
}
]
}

The existing Centreon exporter would remain unchanged and continue to be the primary destination.

The additional exporters would receive the same telemetry in parallel.

 

 

We can have so this benefits

  • Single agent deployment for multiple observability platforms.
  • No duplicated data collection.
  • Reduced CPU and memory footprint compared to running multiple agents.
  • Better integration with the OpenTelemetry ecosystem.
  • Easier adoption of hybrid monitoring architectures.
  • No impact on existing CMA deployments (fully backward compatible).