Skip to content

Commit

Permalink
Update network-versa-director-restapi.md
Browse files Browse the repository at this point in the history
  • Loading branch information
@lucie-dubrunfaut
lucie-dubrunfaut authored Dec 19, 2024
1 parent 584a5d1 commit 93d17e6
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions pp/integrations/plugin-packs/procedures/network-versa-director-restapi.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -450,7 +450,7 @@ All generic options are listed here:
| --verbose | Display extended status information (long output). |
| --debug | Display debug messages. |
| --filter-perfdata | Filter perfdata that match the regexp. Example: adding --filter-perfdata='avg' will remove all metrics that do not contain 'avg' from performance data. |
| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\\{variable\/} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. |
| --filter-perfdata-adv | Filter perfdata based on a "if" condition using the following variables: label, value, unit, warning, critical, min, max. Variables must be written either %\{variable\/} or %(variable). Example: adding --filter-perfdata-adv='not (%(value) == 0 and %(max) eq "")' will remove all metrics whose value equals 0 and that don't have a maximum value. |
| --explode-perfdata-max | Create a new metric for each metric that comes with a maximum limit. The new metric will be named identically with a '\_max' suffix). Example: it will split 'used\_prct'=26.93%;0:80;0:90;0;100 into 'used\_prct'=26.93%;0:80;0:90;0;100 'used\_prct\_max'=100%;;;; |
| --change-perfdata --extend-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back |
| --change-perfdata | Change or extend perfdata. Syntax: --extend-perfdata=searchlabel,newlabel,target\[,\[newuom\],\[min\],\[max\]\] Common examples: =over 4 Convert storage free perfdata into used: --change-perfdata='free,used,invert()' Convert storage free perfdata into used: --change-perfdata='used,free,invert()' Scale traffic values automatically: --change-perfdata='traffic,,scale(auto)' Scale traffic values in Mbps: --change-perfdata='traffic\_in,,scale(Mbps),mbps' Change traffic values in percent: --change-perfdata='traffic\_in,,percent()' =back |
Expand Down Expand Up @@ -514,9 +514,9 @@ All available options for each service template are listed below:
| --filter-device-name | Filter device by name (can be a regexp). |
| --filter-device-type | Filter device by type (can be a regexp). |
| --add-paths | Add path statuses count. |
| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\\{ping\_status\/}, %\\{services\_status\/}, %\\{sync\_status\/}, %\\{controller\_status\/}, %\\{path\_status\/}, %\\{display\/} |
| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\\{ping\_status\/}, %\\{service\_sstatus\/}, %\\{sync\_status\/}, %\\{controller\_status\/}, %\\{path\_status\/}, %\\{display\/} |
| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\\{ping\_status\/} ne "reachable" or %\\{services\_status\/} ne "good"'). You can use the following variables: %\\{ping\_status\/}, %\\{services\_status\/}, %\\{sync\_status\/}, %\\{controller\_status\/}, %\\{path\_status\/}, %\\{display\/} |
| --unknown-status | Define the conditions to match for the status to be UNKNOWN. You can use the following variables: %\{ping\_status\/}, %\{services\_status\/}, %\{sync\_status\/}, %\{controller\_status\/}, %\{path\_status\/}, %\{display\/} |
| --warning-status | Define the conditions to match for the status to be WARNING. You can use the following variables: %\{ping\_status\/}, %\{service\_sstatus\/}, %\{sync\_status\/}, %\{controller\_status\/}, %\{path\_status\/}, %\{display\/} |
| --critical-status | Define the conditions to match for the status to be CRITICAL (default: '%\{ping\_status\/} ne "reachable" or %\{services\_status\/} ne "good"'). You can use the following variables: %\{ping\_status\/}, %\{services\_status\/}, %\{sync\_status\/}, %\{controller\_status\/}, %\{path\_status\/}, %\{display\/} |
| --warning-* --critical-* | Thresholds. Can be: 'total','memory-usage', 'memory-usage-free', 'memory-usage-prct', 'disk-usage', 'disk-usage-free', 'disk-usage-prct', 'alarms-critical', 'alarms-major', 'alarms-minor', 'alarms-warning', 'alarms-indeterminate', 'bgp-health-up' 'bgp-health-down' 'bgp-health-disabled' 'path-health-up' 'path-health-down' 'path-health-disabled' 'service-health-up' 'service-health-down' 'service-health-disabled' 'port-health-up' 'port-health-down' 'port-health-disabled' 'reachability-health-up' 'reachability-health-down' 'reachability-health-disabled' 'interface-health-up' 'interface-health-down' 'interface-health-disabled' 'ike-health-up' 'ike-health-down' 'ike-health-disabled' 'config-health-up' 'config-health-down' 'config-health-disabled' 'packets-dropped-novalidlink', 'packets dropped by sla action', 'paths-up', 'paths-down'. |

</TabItem>
Expand Down

0 comments on commit 93d17e6

Please sign in to comment.