Recently active topics

Hello,The plugin does not report alarms from the DeviceManager of my OceanProtect X8000:  Do you have plans for an improvement to the plugin or an alternative solution?Thanks

L’agent CMA ne prend pas les time periods check configurées, ni les force check car les sondes sont passives, mais malheureusement dans de nombreux cas de figures pour remplacer définitivement les sondes NRPE et SNMP, les time periods sont indispensables, les forces checks appréciés également pour vérifier rapidement un état.

Hi,It’s be possible to give the possibility to change the size of the icons below 84x84 of hosts, services and BAM?We have seen that it’s possible to use geometric shapes but they are limited to 20x20. So, impossible to have icons between 20 and 84?The triangle format of the geometric shape of the services is also confusing and can be misleading in assuming that it is a trend.Best regards

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 benefitsSingle 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 i

HelloCould SUSE Linux be added to the supported Linux distros for the CMA? Regards.

Hello, I would like to suggest an improvement regarding graph rendering consistency between the Resource Status view and the Centreon MAP view. Current behaviorFor the same service and the same metric, graphs displayed from the Resource Status page automatically convert values into human-readable units.Example:Traffic values are displayed in Mb/s on the graph axis and legend.However, when the same graph is displayed in Centreon MAP, the rendering uses the raw metric values and keeps the axis label in b/s, resulting in very large numbers and a graph that is more difficult to read. ExampleResource Status view:95.37 Mb/s 190.73 Mb/s 286.1 Mb/sMAP view:95,370,000 b/s 190,730,000 b/s 286,100,000 b/sThis behavior appears to affect multiple plugins and metrics, not a specific connector. Expected behaviorCentreon MAP should apply the same unit conversion and scaling logic as the Resource Status view, so that:Graph axes are displayed using human-readable units (Kb/s, Mb/s, Gb/s, etc.). The same

Hello.Could a mode be added to the DNS Service connector to get the DNS zone expiration time?Regards.

Hello,I recently noticed within my team that the centagent logs do not include any timezone information.For example:Jun 30 10:41:45 centagent[37466]: [2026-06-30 10:41:45.366] [centreon-monitoring-agent] [info] [main.cc:153] centreon-monitoring-agent start, you can decrease log verbosity by kill -USR1 37466 or increase by kill -USR2 37466.Is there any way to enable timezone information in the centagent log timestamps through the configuration?I checked the agent configuration but I could not find any option related to timezone settings.Thank you for your help.

Dear Centreon, To be able to stop notifications across the entire platform, both central and pollers, I would like to do with a single click instead of configuring mute on each engine. This would be particularly useful in the following contexts:- Centreon update deployment- Custom script update deployment Ideally, if it is possible to program a time maintenance window, that would be even better. Thanks a lot

Get a host/service macro via the v2 API. That seems currently impossible.

Hello all,When creating meta-services, it is possible to use a SQL search for this.But unfortunately this is limited to searching for a "services_description" value.Unfortunately it is not possible to write an expression that would filter the hosts.When I creating meta-services, I would like to be able to filter the hosts or groups of hosts using the "sql search" function. Thanks a lot

Hi Centreon community, Since the acquisition of VMware and the rise in licensing costs, the use of Proxmox has increased dramatically.Unfortunately, the Proxmox monitoring plugin currently falls short of VMware’s.The first major shortcoming is the lack of monitoring for the quorum system: Corosync. And note that it is possible to install a standalone Corosync instance on a Debian system, for example, rather than on a Proxmox node within the cluster, so that it can be hosted at a remote site.The second major difference is the lack of VM monitoring from Proxmox hosts. Only the hosts’ resources are monitored.And the third shortcoming is the autodiscover system, which works perfectly on VMware and is a real advantage. Regards, Phil

Hello,I've made some modifications to your Proxmox VE plugin so that our VMs' tags can be reported in host discovery, but this requires editing database tables. Currently, the data is being reported correctly as raw data in our host discovery.I would like this feature to be officially supported and manageable via the web interface. We’re coming from VMware, and there are a lot of missing features.I’m sharing the changes I made here.centreon_proxmox_ve_restapi.plhttps://github.com/why-grumble/centreon_proxmox_ve_restapi/commit/4e44ae923b51cd73d3b5250b70ed3b5be5992ef2