Skip to main content

    Filter by idea status

    Filter by product

    601 Ideas

    DJ00LSteward *

    columns are not displayed by default in Resource StatusNeeds Votes

    Hello,In the “Resources Status” screen, the “Note” and “Action” columns are not displayed by default. The user must add them manually. If filled in, these ‘Note’ and “Action” fields allow you to add notes or links to URLs. In our case, we use them to link to procedures related to the alert or to provide additional information about the alert. This is very useful for business supervision.It would be a good idea to allow the administrator to add columns for users in the “resources status” menu. This would mean that users would not have to add them themselves and there would be no dependence on the browser.What do you think? Bonjour,Dans l'écran "Statuts des ressources", les colonnes "Note" et "Action" ne sont pas affiché par défaut. C'est à l'utilisateur des les ajouter manuellement. Ces champs "Note" et Action" si elles sont renseignées, permettent d'ajouter des notes ou des liens vers des URL. Dans notre cas nous les utilisons pour cliquer vers des procédures en lien avec l'alerte ou donner des informations complémentaire sur l'alerte. C'est très utile pour la supervision des métiers.Il serait judicieux de laisser à l'administrateur la possibilité d'ajouter des colonnes pour les utilisateurs dans le menu "statuts des ressources". Et ainsi ne pas demander aux utilisateurs de les ajouter eux-même et ne pas garder de dépendance avec le navigateur.Qu'en pensez-vous ?

    cvuilleminSteward *

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

    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.

    katskaSteward ***

    --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan interface filterReleased

    Hi,Could you please add interface filter to --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan.Currently it is only possible to filter by ID, VDom and Name. We have devices where only MPLS is active or only Inet is active. For example:checking sd-wan 'emea_hub' [vdom: root] [interface: emea-inet]    state: up    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s    latency: 53.682ms    jitter: 0.072ms    packet loss: 0.000%checking sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls]    state: down    traffic in: 0.00 b/s, out: 0.00 b/s, bi: 0.00 b/s    latency: 0.000ms    jitter: 0.000ms    packet loss: 100.000% If I filter using name as emea_hub I will get critical alert. So I need to filter by interface name. bash-5.1$ /usr/lib/centreon/plugins//centreon_fortinet_fortigate.pl --plugin=network::fortinet::fortigate::snmp::plugin --mode=sdwan --hostname=1.2.3.4 --snmp-version='2c' --snmp-community='acb'  --warning-traffic-in='' --critical-traffic-in='' --warning-traffic-out='' --critical-traffic-out='' --warning-traffic-bi='' --critical-traffic-bi='' --warning-latency='' --critical-latency='' --warning-jitter='' --critical-jitter='' --warning-status='' --critical-status='%{state} eq "down"' --warning-packetloss='' --critical-packetloss=''  --verbose --filter-name=emea_hubCRITICAL: sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls] state: down | 'root~emea_hub~emea-inet#sdwan.latency.milliseconds'=53.69ms;;;0; 'root~emea_hub~emea-inet#sdwan.jitter.milliseconds'=0.04ms;;;0; 'root~emea_hub~emea-inet#sdwan.packetloss.percentage'=0.000%;;;0;100 'root~emea_hub~emea-mpls#sdwan.latency.milliseconds'=0.00ms;;;0; 'root~emea_hub~emea-mpls#sdwan.jitter.milliseconds'=0.00ms;;;0; 'root~emea_hub~emea-mpls#sdwan.packetloss.percentage'=100.000%;;;0;100checking sd-wan 'emea_hub' [vdom: root] [interface: emea-inet]    state: up    traffic traffic-in : Buffer creation, traffic-out : Buffer creation, traffic-bi : Buffer creation    latency: 53.687ms    jitter: 0.043ms    packet loss: 0.000%checking sd-wan 'emea_hub' [vdom: root] [interface: emea-mpls]    state: down    traffic traffic-in : Buffer creation, traffic-out : Buffer creation, traffic-bi : Buffer creation    latency: 0.000ms    jitter: 0.000ms    packet loss: 100.000%