# Encountered multiple issues trying to set an alarm on bandwidth overuse using snmp fetched metric **URL:** \ **Category:** Help\ **Tags:** agent-alarms, agent\ **Created:** [March 22, 2021, 2:51pm UTC](https://community.netdata.cloud/t/encountered-multiple-issues-trying-to-set-an-alarm-on-bandwidth-overuse-using-snmp-fetched-metric/1103 "2021-03-22T14:51:27Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Ofir\_Marcus](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ofir_marcus/32/620_2.png) [@Ofir\_Marcus](https://community.netdata.cloud/u/Ofir_Marcus)\ **Post date:** [March 22, 2021, 2:51pm UTC](https://community.netdata.cloud/t/encountered-multiple-issues-trying-to-set-an-alarm-on-bandwidth-overuse-using-snmp-fetched-metric/1103/1 "2021-03-22T14:51:28Z")
## Environment Running `netdata/netdata:v1.29.3` docker image on top of aarch64 architecture ## Problem/Question This is the snmp.conf I use for collecting my router BW info (faked some data for security reasons): ```auto { "enable_autodetect": false, "update_every": 5, "max_request_size": 100, "servers": [ { "hostname": "192.161.1.1", "community": "my_comunity", "update_every": 10, "max_request_size": 50, "options": { "timeout": 10000 }, "charts": { "snmp.lte1_tx_rx_rate": { "title": "SNMP Bandwidth for lte1", "units": "kilobits/s", "type": "area", "priority": 1, "family": "mikrotik", "dimensions": { "in": { "oid": "1.3.6.1.2.1.31.1.1.1.6.5", "algorithm": "incremental", "multiplier": 8, "divisor": 1024, "offset": 0 }, "out": { "oid": "1.3.6.1.2.1.31.1.1.1.10.5", "algorithm": "incremental", "multiplier": -8, "divisor": 1024, "offset": 0 } } } } } ] } ``` Inspired by: [https://www.who-els.co.za/2019/06/netdata-snmp-mikrotik.html](https://www.who-els.co.za/2019/06/netdata-snmp-mikrotik.html) Let x = average rate from the last day bw = total bw over a month assuming daily rate is x (and it doesn’t change) if bw \> 50 GB: warn if bw \> 70 GB: critical as for the calculation of x, I encountered some issues and had to split it to two calculations, also I configured the calculation to run every 12 hours. See following config, which is my best attempt defining the alarm: ```auto alarm : monthly_bandwidth_rate_in on: snmp.lte1_tx_rx_rate lookup: average -1d every 10s unaligned absolute of in info: monthly BW average kilobits/s of in to: sysadmin alarm : monthly_bandwidth_rate_out on: snmp.lte1_tx_rx_rate lookup: average -1d every 10s unaligned absolute of out info: monthly BW average kilobits/s of out to: sysadmin alarm : monthly_bandwidth on: snmp.lte1_tx_rx_rate every: 12h calc: ($monthly_bandwidth_rate_out + $monthly_bandwidth_rate_in) * 60 * 60 * 24 * 30 / 8 / 1024 / 1024 units: Gbyte warn: $this > 50 crit: $this > 70 info: monthly BW average GB/month to: sysadmin alarm : monthly_bandwidth_fake1 on: snmp.lte1_tx_rx_rate every: 12h calc: ($monthly_bandwidth_rate_out + $monthly_bandwidth_rate_in) warn: $this > 50 crit: $this > 70 info: monthly BW average GB/month to: sysadmin alarm : monthly_bandwidth_fake2 on: snmp.lte1_tx_rx_rate every: 12h calc: ($monthly_bandwidth_rate_out) warn: $this > 50 crit: $this > 70 info: monthly BW average GB/month to: sysadmin ``` ![netdata](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/1X/b8923fc0594b8455de3d51d90c113bab75ddbb34.png) There are two issues with that resault: 1. `monthly_bandwidth` units are `kilobits/s` and I wasn’t able to change them to anything else 2. The avg calculated is wrong since running the following ```auto curl 'http://10.9.0.6:19999/api/v1/data?chart=snmp.lte1_tx_rx_rate&points=1&&group=average&after=-86400d&before=0' --compressed --insecure { "labels": ["time", "in", "out"], "data": [ [1616371200, 11.4808157, -2.3677532] ] } ``` resulted in different average values: 11.4808157 and abs(-2.3677532) using api vs 1.08 and 0.77 in my defined alarms I am not sure how to proceed and debug this issues . Any help would be appreciated ---
**Author:** ![ilyam8](https://yyz1.discourse-cdn.com/flex029/user_avatar/community.netdata.cloud/ilyam8/32/134_2.png) [@ilyam8](https://community.netdata.cloud/u/ilyam8)\ **Post date:** [March 22, 2021, 9:22pm UTC](https://community.netdata.cloud/t/encountered-multiple-issues-trying-to-set-an-alarm-on-bandwidth-overuse-using-snmp-fetched-metric/1103/2 "2021-03-22T21:22:18Z")
Hi @Ofir_Marcus I tested it with the following alarms (have no network devices, so using my server network bandwidth metrics). ```auto template: 1h_traffic_average_rate_in on: net.net lookup: average -1h unaligned absolute of received calc: $this / 1000 units: Megabits/s every: 10s info: average rate for the last hour to: sysadmin template: 1h_traffic_average_rate_out on: net.net lookup: average -1h unaligned absolute of sent calc: abs($this) / 1000 units: Megabits/s every: 10s info: average rate for the last hour to: sysadmin template: 1h_traffic_average_rate on: net.net calc: $1h_traffic_average_rate_in + $1h_traffic_average_rate_out units: Megabits/s every: 10s info: average rate for the last hour to: sysadmin template: day_traffic_predict on: net.net calc: $1h_traffic_average_rate * 60 * 60 * 24 / 8000 every: 10s units: Gigabytes every: 10s info: predicted total traffic for the upcoming day to: sysadmin template: week_traffic_predict on: net.net calc: $1h_traffic_average_rate * 60 * 60 * 24 * 7 / 8000 every: 10s units: Gigabytes every: 10s info: predicted total traffic for the upcoming week to: sysadmin template: month_traffic_predict on: net.net calc: $1h_traffic_average_rate * 60 * 60 * 24 * 30 / 8000 every: 10s units: Gigabytes every: 10s info: predicted total traffic for the upcoming 30 days to: sysadmin ``` ![Screenshot 2021-03-23 at 00.17.48](https://canada1.discourse-cdn.com/flex029/uploads/netdata2/original/1X/dc4bc34dedfeda052bf491b771c9e0c9dbbc58fa.png) i get the same data (average in, out for the last hour). ```nohighlight [ilyam@pc health.d]$ curl 'http://127.0.0.1:19999/api/v1/data?chart=net.wlp5s0&points=1&after=-3600&options=absolute&options=unaligned' { "labels": ["time", "received", "sent"], "data": [ [1616447455, 1093.0917114, 80.8864254] ] } ``` * * * if you use `unaligned absolute` in the alarms don’t forget to ad `options=absolute&options=unaligned` to your query.