Recently active topics

Hi, when I open a host's  ticket via open-tickets  using dashboard or via notification connector centreon_notification_centreon_opentickets_api.pl , only the host receives the ACK, even though the default acknowledgement configuration is set to “acknowledge services attached to the host”.My idea is to make the open-tickets ACK to respect the default acknowledgement configuration for hosts, or this parameter should be configurable within the provider rule.

Bonjour à tous,Je souhaite proposer une amélioration pour Centreon Map qui, je pense, pourrait bénéficier à de nombreux utilisateurs.Contexte : Actuellement, Centreon Map limite la taille des images à 2MB et ne supporte pas les fichiers SVG. Cette restriction pose des défis lorsque nous voulons intégrer des images de haute qualité ou des graphiques vectoriels, qui sont souvent essentiels pour une visualisation claire et précise de notre infrastructure.Proposition d'amélioration :Augmenter la taille maximale des images supportées au-delà de 2MB : Avec l'augmentation des résolutions d'écran et la nécessité d'images détaillées, il serait bénéfique de permettre l'importation d'images de plus grande taille. Cela éviterait la perte de qualité due à la compression excessive. Supporter les fichiers SVG : Les SVG (Scalable Vector Graphics) sont des graphiques vectoriels qui offrent une qualité d'image supérieure à n'importe quelle résolution, sans perte de qualité. En permettant l'utilisation d

Paloalto firewalls use internal ssl certificates. It should be important to monitor this certificates through SSH:admin@fw01-bz> show sslmgr-store config-certificate-infoAF05329B:A856B404C25A48A0C02F0A7A3A2036925B9BA5C2 serial number: issuer: /CN=81.161.232.189 issuer-subjecthash: A856B404C25A48A0C02F0A7A3A2036925B9BA5C2 issuer-keyhash: db-type: V db-exp-date: 321008075404Z(Oct 8 07:54:04 2032 GMT) db-rev-date: () db-serialno: AF05329B db-file: unknown db-name: /CN=vpn.i-vertix.com db-status: V7CE5E3F56B1AB38C4D0BC440823B9E9:273F5E283B4F4D0879716CD0E32A886B8195C0F3 serial number: issuer: /CN=Microsoft Azure Federated SSO Certificate issuer-subjecthash: 273F5E283B4F4D0879716CD0E32A886B8195C0F3 issuer-keyhash: db-type: V db-exp-date: 251011072048Z(Oct 11 07:20:48 2025 GMT) db-rev-date: () db-serialno: 7CE5E3F56B1AB38C4D0BC440823B9E99unknown db-file: unkn

Persona: All users receiving notifications Problem to solve: Default notifications are poorly formatted, no colorization, no highlight... Expected outcome:  Immediate readability of what resource is impacted what is the status Less alert fatigue Potential solutions: https://github.com/Shini31/centreon-notifications or this fork https://github.com/masgo/centreon-notifications Support of markdown-formatted messages Based on Github proposition. 

Hi, I would like to be able to create auto-login URLs that lead directly to the resource status pages rather than to the deprecated status detail pages.The goal would be to provide direct access to the popup displayed when selecting a service from the Resource Status page.At present, only the deprecated status detail pages can be accessed through automatically generated URLs. Regards,Gaël

Hi,Could you add a filter for namespace for plugin cloud::prometheus::exporters::cadvisor::plugin ?The name of namespace is on the output when we list-containers, so it will be easy to add the filter :)  /usr/lib/centreon/plugins//centreon_prometheus_cadvisor_api.pl --plugin=cloud::prometheus::exporters::cadvisor::plugin  --mode=cpu --hostname=*** --url-path='/api/v1' --port='80' --proto='http' --credentials --username=*** --password=***  --container='container=~"moncontainer"' --pod='pod=~".*"'  --verbose --mode=list-containers [container_name = moncontainer][pod_name = monpod-55d94dc4cc-rtmxg][namespace = MONNAMESPACE]Thanks a lot 

Bonjour,Nous sommes dans une infrastructure hybride Cloud Azure / OnPrem. De ce fait nous avons pas mal de base de données Cloud Azure et nous utilisons donc le connecteur dédié.Le connecteur Azure SQL Database propose notamment de surveiller la consommation CPU et RAM des BDD mais pour nos utilisateurs des équipes projet applicatif ces métriques ne sont pas pertinentes Pour eux il est beaucoup plus pertinent de surveiller la consommation DTU des bases de données Azure.Donc lorsqu’il y a une mise en production d’une application et qu’elle comprend une BDD Azure, les équipes nous demandent systématiquement de monitorer la consommation DTU.Actuellement nos monitorons cette consommation DTU mais via des check custom avec script ps1 avec une exécution distante en NRPE.  C’est donc pour cette raison que je me permet de vous faire cette proposition de création de commande de check DTU. Cette métriques étant systématiquement demandée, je pense qu’il serait intéressant et pertinent de le rajou

Hi, We have configured parent-child relationships between hosts, and we would like this parentage information to be visible somewhere in the Resources Status page.This could be implemented, for example, as:An additional column showing the parent/child relationship for each host, and/or Additional information displayed in the side panel when selecting a host/serviceThis would make it easier to quickly identify dependency relationships between hosts directly from the Resources Status view, without having to navigate to another page. Regards,Thomas

Hi, We have noticed a visual inconsistency in the monitoring interface regarding the color used to represent hosts in an Unreachable state (child hosts whose parent host is Down). In the top banner (Hosts counter), unreachable hosts are counted and displayed in orange. In Resource Status, the same hosts display an Unreachable status badge in grey. This is confusing for operators.Aligning the color of the Unreachable status across the top banner and the Resource Status page would make things much easier for our operators. Would it be possible to implement this? Regards,Thomas

Hello,Currently, we can retrieve the macros from the services by targeting the service itself in the endpoint : /api/latest/configuration/services/{service.id}.The macros are absent when checking for several services : /api/latest/configuration/servicesWould it be possible to add an option to fetch the macros in that endpoint ? Currently, if we want to retrieve the macros from the configuration, we have to make a request for each service.

Sometimes the team that administrate Centreon is different from the ones that make the daily configuration, like adding new host.This could lead to some scenario where you have overused pollers and underused pollers.Maybe we can add a feature that could “lock a poller”:The default poller can not be locked and viceversa. You can’t see nor select a locked poller if you add a new host If you duplicate an host monitored by a locked poller, it will lbe monitored by the default. Thanks for reading!

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,Please add native probes for XCP-NG hypervisor and Xen Orchestra management platform in Centreon. These would enable monitoring of hosts, VMs, storage, and performance metrics similar to existing VMware/Proxmox support. Essential for XCP-NG users. Thank you!