Build better products with our product team.
Right now when a use is on Centreon and wants to create a host, the only component they can use to decide what to implement is the Template select field.This is a little bit raw to let users discover what they want to install.In a similar way as Connectors or the new wizard for pollers, i would like to be able to let users go in a cleaner interface to choose what template they are looking to implement.This could take many forms as it’s more related to how the UI would show the information to the user and i’m unsure how easily we can structure this from the list of templates.But this is my idea, to avoid the hassle of the user going through documentation to find what host template to use, to prefer to stay on the centreon and go through a wizard to choose what template to integrate. What does the community think of this ?
Persona:Centreon administratorProblem to solve:In the current NetApp Ontap REST API – volumes mode, thresholds are calculated based only on the current volume size.For volumes with autogrow enabled, this makes percentage usage misleading since the effective limit is defined by the autosize maximum setting.Current behavior:The plugin retrieves size but does not consider the autosize object returned by the ONTAP REST API.Example from a production environment (anonymized):"autosize": { "maximum": 274877906944, "minimum": 10737418240, "grow_threshold": 85, "shrink_threshold": 50, "mode": "grow_shrink" } Expected outcome:Allow the plugin to use autosize.maximum as an optional reference for threshold calculation.Users could choose between: Default: thresholds based on the current volume size. Optional: thresholds based on the autosize.maximum value. Potential solutions: Extend the REST query to include autosize.maximum from /api/storage/volumes (API reference). Add a new option (e.g. --use-autosize-maximum or similar). Adjust perfdata labels to clearly distinguish between both reference types. Benefits / Impact: Enables accurate monitoring of autogrow volumes. Prevents false alerts when volumes expand automatically. Aligns threshold logic with NetApp’s operational behavior, improving reliability in large environments.
Usefull when you debug some problem on your centreon .It could be insteresting to find with host Id or Service Id your object on resource status page
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, A nice feature would be to be able to use macros within custom macros.For example use $hostname$ in a URL like this in order to use the hostname do dynamically create the URL.Thanks in advance for the consideration.
The personal filters on the resource status page are great, but it's not easy to share them with other users.Sharing the URL or content of the search filter is sometimes considered complicated for some users, despite the apparent ease of the operation.A sharing feature similar to that used in dashboards would be a plus in terms of usability.In addition, being able to use these filters directly in the dashboard resource grid widget would allow for even greater customization. Currently, only standard filters are available.
Bonjour,Les dashboards de pilotage sont dans l’air du temps et avoir d’autres styles de graphe sur centreon serait top : Exemple : Bulles de dispersion : Graphes de points : Camembert : Cordialement,
Hello,I would like the name of a token to appear in the Administration logs section of the Centreon Cloud platform, perhaps by adding an additional column or through another method.This feature would be appreciated, especially when you have multiple tokens in production.
Rubrik 9.4+ now moves many on‑prem clusters to RSC‑only management, disabling local CDM REST APIs. As a result, the current Centreon Rubrik REST API plugin cannot monitor these environments, since it only supports CDM clusters and not the RSC console.Rubrik officially transitioned from REST to GraphQL APIs for RSC management and recommends using GraphQL for monitoring.A GitHub issue already requests GraphQL support for the Centreon plugin, but no RSC‑compatible plugin exists yet.Request:Please add an official Centreon Plugin Pack supporting Rubrik Security Cloud (RSC) using GraphQL and RSC authentication (client_id / client_secret).Thank you!
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK