added ifl in out errors and traffic fields #868
Conversation
|
Only Juniper employees can contribute to juniper_official folder. If you are one follow the steps mentioned in the README else, contribute to the community_supplied directory. Make the necessary changes and commit again. |
| description "Subinterface operational status"; | ||
| } | ||
| } | ||
| field high-threshold { |
There was a problem hiding this comment.
rename to traffic-high-threshold
| } | ||
| field in-errors-threshold { | ||
| constant { | ||
| value "{{errors-threshold-variable}}"; |
There was a problem hiding this comment.
Cannot find this variable
| path /interfaces/interface/subinterfaces/subinterface/state/counters/in-errors; | ||
| zero-suppression; | ||
| } | ||
| type integer; |
There was a problem hiding this comment.
Shouldn't this be uint?
| path /interfaces/interface/subinterfaces/subinterface/state/counters/in-octets; | ||
| zero-suppression; | ||
| } | ||
| type integer; |
| type float; | ||
| description "Utilization in percentage which derived based on mbps and interface speed"; | ||
| } | ||
| field low-threshold { |
There was a problem hiding this comment.
change to traffic-low-threshold
| } | ||
| field out-errors-threshold { | ||
| constant { | ||
| value "{{errors-threshold-variable}}"; |
There was a problem hiding this comment.
Can't find this variable
| path /interfaces/interface/subinterfaces/subinterface/state/counters/out-octets; | ||
| zero-suppression; | ||
| } | ||
| type integer; |
| description "Sub interfaces index to be monitored, regular expression, eg '0-10'"; | ||
| type string; | ||
| } | ||
| variable traffic-high-threshold { |
There was a problem hiding this comment.
Why are we using thresholds where there are no triggers? What is the porpose here? Only collecting the data without any evaluations????
|
Jenkins please retry a build |
4 participants
added ifl in out errors and traffic fields