Brian S
2013-01-31 19:47:38 UTC
Brian S [http://community.zenoss.org/people/z3r0day] created the discussion
"Custom Throughput Monitoring"
To view the discussion, visit: http://community.zenoss.org/message/71324#71324
--------------------------------------------------------------
Hi Everyone,
I'd like to create custom monitoring templates with a custom utilization threshold to alert if the throughput of an interface goes above it.
The links that are to be monitored are microwave links that have a defined throughput limit. We want to know when, say, 80% of throughput is being reached so we can plan ahead to upgrade the link. I did some research, and below is what I've done so far; though I feel it is flawed. I'd like to hear everyone's feedback and suggestions/recommendations.
For example, there is a group of microwaves that have a 3mbps max throughput. I created a custom schema called "cLinkMaxThroughputMbps". I then created a class /Device/MW/3Mbps and set the cLinkMaxThroughputMbps value to 3.0 for this class. In Advanced --> Monitoring Templates, I took the ethernetCsmacd template and used the "overwrite template" feature to copy the template to the class /Device/MW/3Mbps. I then changed the high utilization threshold Maximum Value to ((here.cLinkMaxThroughputMbps) / 8 * 1024 * 1024) * .8. This will give me the value in Bytes per second, and multiply it by the threshold of 80% to set the alarm value.
When this is implemented, I get the following alarm in Zenoss. Regardless of the alarm, I've seen the threshold alarms appear, as if the threshold is working correctly. Eventually, the alarm stops coutings and everything seems to work normally. Although, I've only tested on a few devices.
http://community.zenoss.org/servlet/JiveServlet/showImage/2-71324-14813/zen-python-error.bmp http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-71324-14813/450-22/zen-python-error.bmp
If I look back at the edited threshold, I see an error about the InOutOctets_InOutOctets(missing).
http://community.zenoss.org/servlet/JiveServlet/showImage/2-71324-14814/zen-octetsmissing-error.bmp http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-71324-14814/450-494/zen-octetsmissing-error.bmp
Can some one let me know why these errors are occurring, and if there is a better way to go about this custom throughput monitoring?
Thanks!
z3r0day
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71324#71324]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
"Custom Throughput Monitoring"
To view the discussion, visit: http://community.zenoss.org/message/71324#71324
--------------------------------------------------------------
Hi Everyone,
I'd like to create custom monitoring templates with a custom utilization threshold to alert if the throughput of an interface goes above it.
The links that are to be monitored are microwave links that have a defined throughput limit. We want to know when, say, 80% of throughput is being reached so we can plan ahead to upgrade the link. I did some research, and below is what I've done so far; though I feel it is flawed. I'd like to hear everyone's feedback and suggestions/recommendations.
For example, there is a group of microwaves that have a 3mbps max throughput. I created a custom schema called "cLinkMaxThroughputMbps". I then created a class /Device/MW/3Mbps and set the cLinkMaxThroughputMbps value to 3.0 for this class. In Advanced --> Monitoring Templates, I took the ethernetCsmacd template and used the "overwrite template" feature to copy the template to the class /Device/MW/3Mbps. I then changed the high utilization threshold Maximum Value to ((here.cLinkMaxThroughputMbps) / 8 * 1024 * 1024) * .8. This will give me the value in Bytes per second, and multiply it by the threshold of 80% to set the alarm value.
When this is implemented, I get the following alarm in Zenoss. Regardless of the alarm, I've seen the threshold alarms appear, as if the threshold is working correctly. Eventually, the alarm stops coutings and everything seems to work normally. Although, I've only tested on a few devices.
http://community.zenoss.org/servlet/JiveServlet/showImage/2-71324-14813/zen-python-error.bmp http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-71324-14813/450-22/zen-python-error.bmp
If I look back at the edited threshold, I see an error about the InOutOctets_InOutOctets(missing).
http://community.zenoss.org/servlet/JiveServlet/showImage/2-71324-14814/zen-octetsmissing-error.bmp http://community.zenoss.org/servlet/JiveServlet/downloadImage/2-71324-14814/450-494/zen-octetsmissing-error.bmp
Can some one let me know why these errors are occurring, and if there is a better way to go about this custom throughput monitoring?
Thanks!
z3r0day
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/71324#71324]
Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]
