Build better products with our product team.
Hi everyone,I’d like to suggest an enhancement for the CSV export feature in Centreon.Currently, when exporting service or host lists to CSV, the file does not include the Host ID or Service ID, which are often needed when working with the API, automation scripts, or external integrations.Requested improvement:Add two optional columns to CSV exports: host_id service_id This would make it much easier to correlate exported data with REST API queries or configuration automation tools.
Bonjour, Nous recherchons un plugin pour que Centreon envoie des tickets via open ticket vers Matrix42 sur un connecteur personnalisé ou une configuration à faire via son API (ou Service Bus) Sachant que : Matrix42 propose également une API REST et des mécanismes de Web Services pour la création ou la mise à jour de tickets. On pourrait s’en servir pour injecter des tickets automatiquement depuis Centreon. Avoir sinon un Plugin dédiéÀ ce jour, il n'existe pas de plugin natif ou officiel directement entre Centreon et Matrix42 (comme il en existe pour ServiceNow ou GLPI, par exemple).
Veeam has released version 13, which is no longer compatible with the current Centreon connectors.In this version, access is only available through the REST API:https://helpcenter.veeam.com/references/vbr/13/rest/1.3-rev0/tag/LoginVeeam is now provided as a Linux appliance with specific command sets.Could you please consider updating the Centreon plugin to support this new version and its REST API access?
Hello,Many modern Linux systems that are part of systemd have the systemd-timesyncd service.If this service is used, then there are no such things as ntpd and chronyd in the system.Please extend the "ntp" mode to work with the timedatectl utility.# timedatectl status Local time: Fri 2022-10-07 18:33:28 MSK Universal time: Fri 2022-10-07 15:33:28 UTC RTC time: Fri 2022-10-07 15:33:28 Time zone: Europe/Moscow (MSK, +0300)System clock synchronized: yes NTP service: active RTC in local TZ: no # timedatectl timesync-status Server: 10.10.0.2 (srv-ntp.holding.com)Poll interval: 34min 8s (min: 32s; max 34min 8s) Leap: normal Version: 3 Stratum: 3 Reference: A05A409 Precision: 1us (-23)Root distance: 128.654ms (max: 5s) Offset: +6.303ms Delay: 1.544ms Jitter: 16.867ms Packet count: 17 Frequency: +1.635ppm Thank you.
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 impact on existing CMA deployments (fully backward compatible).
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.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.