Build better products with our product team.
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.
Hello, We are missing a way in the UI, where a list of services/templates can be found, filtered by a particular Command that is being referenced.The usage scenario is making sure that changes to the underlying Command do not break the existing hosts when they get regenerated in the future. The existing list of Commands with just a reference count is far from being fit for the purpose. Thank you. BR, Lubos MedovarskyScheidt & Bachmann
Currently, MIB data is not sufficient, and it would be useful to be able to monitor the appliance and the buckets.Actuellement la MiB n'est pas suffisante et il serait intéressant de pouvoir superviser l'appliance et les buckets.
Bonjour,Les courbes de graphes sont actuellement adaptés pour une interface en mode “light” mais en mode “dark”, les courbes en gris, noir, bleu foncé, ne sont pas très visibles.Je sais qu’on peut changer les couleurs des courbes mais le changement s’applique aussi au mode “light” et donc changer une courbe noir en blanc va reporter le problème sur les utilisateurs en mode “light”.Est-il possible que les couleurs par défaut s’adaptent en fonction du mode choisi par l’interface ? Et/ou qu’il soit possible de choisir 2 couleurs différentes pour une même courbe, selon que l’interface est configurée en mode “light” ou “dark” ?Merci d’avance
HiIn service and host macros, certain characters must be escaped because they are suppressed or stripped when used in commands. Typically, exclamation marks require a backslash when used in passwords.However, when performing auto-discovery, you need to remove the backslash for it to work.Would it be possible to standardize things so that there is no need to escape certain special characters in macros or arguments?
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,To improve the connector Veeam One REST API, I would suggest these improvements :Add a --filter-backup-server-id parameter to filter jobs by VBR instance.The backupServerId field exists in the API response but is not usable for filtering.This would allow to independently monitor the different backup servers.Example: --filter-backup-server-id='1' or --filter-backup-server-id='1|2' (regex)Add the lastRun timestamp to the plugin output and support alerting thresholds on it.The lastRun field exists in the API but is not displayed.This would allow to alert if a backup has not run for X hours.Proposed parameter examples: --critical-job-last-run='> 24h', --critical-job-never-run=yes
Bonjour,L’idée est de remonter le champs snmp sysLocation.0 des equipements dans le host discovery afin de mettre le mapper Host Extended Infos ==> Geographic coordinates. sysLocation.0 dans le host discoveryvers Host Extended Infos ==> Geographic coordinates Je mets actuellement le champs sysLocation par une localisation sur mes equipements, cela permetterai de faire une carte geographique automatique. Cordialement
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.