Build better products with our product team.
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?
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,In the widgets “Host Monitoring” or “Service Monitoring” for the Custom Views, we have icons for the links in Note_URL et Action_URL.In widget Resources_Table for the Dashboard, we don’t have these icons, however in my organisation we use its for the troubleshooting.Can theses icons be added in the widget Resources_Table ?Thanks
Hi,My company is using more and more API with Centreon for reporting.We can export automaticaly some KPIs, but actualy it’s not supported to export SLA, SLO, availability rate, events for BA.So, it could be great if you can add APIs for request this informations via API
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).
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 à 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 de fichiers SVG, nous pourrions bénéficier de visuels plus nets et plus professionnels dans nos cartes Centreon.Bénéfices attendus :Amélioration de la clarté et de la qualité visuelle des cartes. Possibilité de personnaliser les cartes avec des images plus détaillées et des graphiques vectoriels. Gain de temps pour les administrateurs qui n'auront plus besoin de redimensionner ou convertir des images pour qu'elles respectent les restrictions actuelles.Je suis certain que cette amélioration rendrait Centreon Map encore plus puissant et flexible pour tous les utilisateurs. Merci de prendre en considération cette proposition.Bien cordialement,CASELLATO MATHIEUIngénieur Réseaux & SécuritéOrangeCyberDefense
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!
Hello,Could you configure with your api the functionnality :-Create discovery jobs with parameters by API
Almost exclusively, our team uses poller settings with checkboxed “Move Export Files”, “Restart Monitoring Engine” turned On as shown below: I’m not sure about other people’s needs, but the setting shown is so common during our daily operations, and especially when exports are very frequent - that is, when things don’t work as expected and Configuration File Export becomes a debugging tool - it is quite rare for us to use these checkboxes in a different setting. This proposal suggests implementing configuration settings for default states of the following UI elements:Checkboxes Monitoring Engine restart method and eventually, Post generation command,to improve the UX and make frequent daily exports as smooth as possible. Cumulatively in operations, this change would save a a lot of time and friction when services don’t work as expected and need more time to fix, while this page becomes an unnecessary mental burden in the process. Currently, in order to save us thousands of daily mouse point-and-clicks at these boxes, after each minor update we manually patch the web page to default as show above, for the sake of preserving sanity. Thank you!
Context & Problem: In the new Dashboards, the "Group Monitoring" widget systematically displays all status badges (Down, Up, Critical, Warning, Ok) even when their count is 0.While the new Dashboard Engine is great, displaying these (0) values creates significant visual noise. When monitoring dozens of hostgroups, the screen becomes cluttered with green and red badges that don't actually require any action. It makes it much harder for operators to spot real alerts at a glance.In the legacy Custom Views, the old hostgroup-monitoring widget naturally hid these zero values, offering a much cleaner and efficient UX.Suggested Solution: Please add a simple toggle in the widget configuration panel (e.g., a checkbox: "Hide empty statuses" or "Hide counters at 0").When enabled, the React component would simply not render the badge if the count is exactly 0.Value: This small UI tweak would massively improve the readability of the Dashboards, reduce cognitive load for IT operators, and help teams focus only on actual ongoing issues.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.