Network Management
Current Traffic variables displayed in Bps in alert email
The calculation of Receive and Transmit variables for Current Traffic are displayed as Bits per second (Bps) instead of Megabits per second (Mbps) when added in the email content of alerts after upgrading to NPM v11.5.
First published date
Last published date
Overview
The calculation of Receive and Transmit variables for Current Traffic are displayed as Bits per second (Bps) instead of Megabits per second (Mbps) when added in the email content of alerts after upgrading to NPM v11.5.
- The Node Details page displays the correct calculation in Mbps as shown below:
- The following shows that the variables are added as Bps:
- The following is an example of the email that is received after the alert:
Product section
Cause
Resolution
- Go to Settings > Manage Alerts.
- Select the alert and click Edit Alert.
- Go to Trigger Actions or Reset Actions and click Edit for 'Sending an Email/Page'.
- Under Message, replace ${N=SwisEntity;M=Inbps} and ${N=SwisEntity;M=Outbps} with the following and save the changes:
Received : ${SQL: SELECT CONVERT(NUMERIC(15,2),CONVERT(NUMERIC(15,2),(${N=SwisEntity;M=Inbps}))/1000000)} Mbps Transmitted : ${SQL: SELECT CONVERT(NUMERIC(15,2),CONVERT(NUMERIC(15,2),(${N=SwisEntity;M=Outbps}))/1000000)} MbpsNote: If you are measuring the utilization in Megabits, you can always change the divisor to 1000 for Kbps or even 1000000000 for Gbps if you are in a 10 Gigabyte network. - If you are receiving a MACRO SQL error using the above query, apply a format on the variable like the one below. This will convert bps to the closest metrics possible: For example: If bps can be converted to Gbps, it will show in Gbps instead of just Mbps.
Received : ${N=SwisEntity;M=Inbps;F=Bytes}bps
Transmitted : ${N=SwisEntity;M=Outbps;F=Bytes}bps