Build better products with our product team.
Hello,To interact with Centreon MAP using RestAPI one must authenticate providing a user and password as described in the documentation: https://docs.centreon.com/docs/24.10/api/map-api/ . Only after that a token is generated and provided.We would like to suggest that only a token (created in Administration > Authentication Tokens) is needed to start interacting with Centreon MAP RestAPI so the authentication step with username and password and generating a random token is not needed. Best regards,Jarosław Kęsy
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:Centreon administratorProblem to solve:In the current Linux SSH – Files-Size mode, thresholds are calculated based only on the raw directory size in bytes. For directories subject to operational "soft limits" or logical growth policies (where no system-level quotas are enabled), the lack of a reference capacity makes percentage-based monitoring impossible. This requires administrators to manually recalculate byte-based thresholds whenever a logical limit is adjusted.Current behavior:The plugin retrieves the directory size using the du command via SSH but does not provide a parameter to define a reference capacity. Thresholds are strictly compared against absolute byte counts, and no percentage usage is calculated in the status output or performance data.Expected outcome:Allow the plugin to use a user-defined "Logical Maximum Size" as an optional reference for threshold calculation. Users could choose between: Default: Thresholds based on the raw directory size in bytes. Optional: Thresholds based on a percentage of a manually defined --max-size. Potential solutions: Add a new option (e.g., --max-size) to define the 100% reference value (supporting units like G, M, or bytes). Add a new option (e.g., --use-percentage) to interpret warning and critical inputs as percentage values of the maximum size. Enhance performance data by populating the "max" field of the size metric and adding a dedicated size_prct metric. Update the status output to display the usage ratio (e.g., "Used / Max (Usage %)"). Benefits / Impact: Scalability: Enables the use of generic Service Templates where only a capacity macro is adjusted per host. Operational Clarity: Provides intuitive feedback (percentage of a limit) rather than raw byte counts for operators.
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!
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 ?
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,
referenced tohttps://github.com/centreon/centreon-plugins/issues/6117 I can add more information if required in github issue
Hi,The Fortinet Fortigate SNMP already have the ability to filter sd-wan links by name.W'll be great if a new Disvery Rule to create Services by individual sd-wan links.Using just one service to all sd-wans links can obscure a new CRITICAL error when multiples links fail, and creating one service per sd-wan link can be massive when I manage 500+ Fortigates each with 10+ sdwan link.We need to create SD-WAN services in the same way that we create Interfaces services… Thnaks
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