me2
2012-04-28 15:13:13 UTC
me2 [http://community.zenoss.org/people/me2] created the discussion
"creating data points and data stores how to quickly tell if it should be a gauge or a derive?"
To view the discussion, visit: http://community.zenoss.org/message/66118#66118
--------------------------------------------------------------
hello,
I am looking to tell any easy way if it should be a gauge or a derive.
I haven't been using snmp long enough to easily tell or I dont know the common rule to easily know which one to choose.
I am going to add the below and am looking for guidance.
*LATENCY_AVG_MINUTE, SNMP OID: .1.3.6.1.4.1.15497.1.2.3.7.9.1*
(ASYNCOSWEBSECURITYAPPLIANCE-MIB::cacheTotalRespTimeNow.0)
together with:
*'TRANSACTION_RATE_AVG_MINUTE': .1.3.6.1.4.1.15497.1.2.3.7.1.1*
(ASYNCOSWEBSECURITYAPPLIANCE-MIB::cacheThruputNow.0)
and if possible:
'*BANDWIDTH_AVG_MINUTE': .1.3.6.1.4.1.15497.1.2.3.7.4.1*Â (output is in kbps)
Taking a few known high loaded cluster of WSA the average response time is usual somewhere between 1200 and 5100 ms, however a good alert value should be about 15000 to 30000 ms (15-30 sec).
This should be profiled together with the TRANSACTION_RATE_AVG_MINUTE as the LATENCY_AVG with only marginal traffic is very sensitive to be spoiled with long run request. This again can be avoided by taking BANDWITH_AVG into account also (large downloads will increase latency, however also bandwith usage).
This is important to understand to proper monitor the WSA units within an high performance environment. If there are any questions please feel free to contact us anytime.
Total current connections > is calculated from adding the following two variables
*'CURRENT_TOTAL_CLIENT_CONN': .1.3.6.1.4.1.15497.1.2.3.2.8*
*'CURRENT_TOTAL_SERVER_CONN': .1.3.6.1.4.1.15497.1.2.3.3.8*
If the total sum of this values are increasing dramatically (in factors) of the usual amount without any reasonable change, this may indicate temporary leaks that might worth customer supports attention to follow up.
To setup the initial values our recommendation is to trial these numbers within e.g. one business week in production to determine the typical behavior for your network / group of WSA units. Also, these numbers are good to record to enlighten new possible trends of the user behavior.
thanks,
Jay
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/66118#66118]
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]
"creating data points and data stores how to quickly tell if it should be a gauge or a derive?"
To view the discussion, visit: http://community.zenoss.org/message/66118#66118
--------------------------------------------------------------
hello,
I am looking to tell any easy way if it should be a gauge or a derive.
I haven't been using snmp long enough to easily tell or I dont know the common rule to easily know which one to choose.
I am going to add the below and am looking for guidance.
*LATENCY_AVG_MINUTE, SNMP OID: .1.3.6.1.4.1.15497.1.2.3.7.9.1*
(ASYNCOSWEBSECURITYAPPLIANCE-MIB::cacheTotalRespTimeNow.0)
together with:
*'TRANSACTION_RATE_AVG_MINUTE': .1.3.6.1.4.1.15497.1.2.3.7.1.1*
(ASYNCOSWEBSECURITYAPPLIANCE-MIB::cacheThruputNow.0)
and if possible:
'*BANDWIDTH_AVG_MINUTE': .1.3.6.1.4.1.15497.1.2.3.7.4.1*Â (output is in kbps)
Taking a few known high loaded cluster of WSA the average response time is usual somewhere between 1200 and 5100 ms, however a good alert value should be about 15000 to 30000 ms (15-30 sec).
This should be profiled together with the TRANSACTION_RATE_AVG_MINUTE as the LATENCY_AVG with only marginal traffic is very sensitive to be spoiled with long run request. This again can be avoided by taking BANDWITH_AVG into account also (large downloads will increase latency, however also bandwith usage).
This is important to understand to proper monitor the WSA units within an high performance environment. If there are any questions please feel free to contact us anytime.
Total current connections > is calculated from adding the following two variables
*'CURRENT_TOTAL_CLIENT_CONN': .1.3.6.1.4.1.15497.1.2.3.2.8*
*'CURRENT_TOTAL_SERVER_CONN': .1.3.6.1.4.1.15497.1.2.3.3.8*
If the total sum of this values are increasing dramatically (in factors) of the usual amount without any reasonable change, this may indicate temporary leaks that might worth customer supports attention to follow up.
To setup the initial values our recommendation is to trial these numbers within e.g. one business week in production to determine the typical behavior for your network / group of WSA units. Also, these numbers are good to record to enlighten new possible trends of the user behavior.
thanks,
Jay
--------------------------------------------------------------
Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/66118#66118]
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]