Team INT
[ZBX-16539] Juniper Template CPU utilization Created: 2019 Apr 15 Updated: 2024 Apr 10 Resolved: 2019 Oct 28 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Templates (T) |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.13rc1, 4.2.7rc1, 4.4.0alpha3, 4.4 (plan) |
| Type: | Problem report | Priority: | Minor |
| Reporter: | Levent Karakaş | Assignee: | Anton Fayantsev (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Template_Net_Juniper_SNMPvX, lld, templates, triggers | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Juniper EX3200 |
||
| Team: | Team INT |
| Sprint: | Sprint 56 (Sep 2019), Sprint 55 (Aug 2019), Sprint 57 (Oct 2019) |
| Story Points: | 1 |
| Description |
|
Steps to reproduce: In official Juniper template, CPU utilization is being calculated with jnxOperating5MinLoadAvg (1.3.6.1.4.1.2636.3.1.13.1.21). High CPU trigger is avg(*5m)*}>{$CPU_UTIL_MAX}.
Result: This load can be more than %100 as described here: https://kb.juniper.net/InfoCenter/index?page=content&id=KB31764 Thus it is creating false alarms.
Expected: Usage of jnxOperatingCPU (1.3.6.1.4.1.2636.3.1.13.1.8) instead of jnxOperating5MinLoadAvg (1.3.6.1.4.1.2636.3.1.13.1.21)
|
| Comments |
| Comment by Alexander Vladishev [ 2019 Sep 05 ] |
|
Fixed in:
|