Skip to main content

    Filter by idea status

    Filter by product

    291 Ideas

    GMicasSteward *

    Consistent graph unit conversion between Resource Status and MAP viewsNeeds Votes

    Hello, I would like to suggest an improvement regarding graph rendering consistency between the Resource Status view and the Centreon MAP view. Current behaviorFor the same service and the same metric, graphs displayed from the Resource Status page automatically convert values into human-readable units.Example:Traffic values are displayed in Mb/s on the graph axis and legend.However, when the same graph is displayed in Centreon MAP, the rendering uses the raw metric values and keeps the axis label in b/s, resulting in very large numbers and a graph that is more difficult to read. ExampleResource Status view:95.37 Mb/s 190.73 Mb/s 286.1 Mb/sMAP view:95,370,000 b/s 190,730,000 b/s 286,100,000 b/sThis behavior appears to affect multiple plugins and metrics, not a specific connector. Expected behaviorCentreon MAP should apply the same unit conversion and scaling logic as the Resource Status view, so that:Graph axes are displayed using human-readable units (Kb/s, Mb/s, Gb/s, etc.). The same metric is rendered consistently across all Centreon interfaces. Users can easily compare graph data regardless of where the graph is displayed. BenefitsImproved readability of MAP dashboards. Better user experience and consistency across Centreon products. Reduced confusion when comparing the same metric between Resource Status and MAP views. Thank you for considering this enhancement.Best regards,Gaël MICAS

    cvuilleminSteward *

    Linux SSH Plugin – Add Support for “Logical Maximum Size” and Percentage Thresholds in Files-Size ModeNeeds Votes

    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.