Create a Threshold with variable on Maxium Value

[bjoljo]

bjoljo [http://community.zenoss.org/people/bjoljo] created the discussion

"Re: Create a Threshold with variable on Maxium Value"

To view the discussion, visit: http://community.zenoss.org/message/62676#62676

--------------------------------------------------------------
Maybe you have found a working soloution, I just though that I would share how I solved a similar problem.
<disclaimer> I still use Zenoss 2.5.2 </disclaimer>.

I have a couple of small firewalls that have different licenses regading the number of allowed hosts behind the them. The number of active hosts and the license value of the firewall is availiable through snmp.

I created two data sources. One that polled the number of active hosts and another that polled the license value.
I then created a threshold on the datapoint "active hosts" with the following max value:
here.getRRDValue('MaxAllowedHosts') * .8

MaxAllowedHosts is the data point of my data source that polled the license value.

In the graph I added the data point showing "number of active hosts" and the threshold showing 80% of the license value.

This might not be the ultimate soloution for you but it works for me :)

Regards
Björn
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62676#62676]

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]

[Shane Scott]

Shane Scott [http://community.zenoss.org/people/hackman238] created the discussion

"Re: Create a Threshold with variable on Maxium Value"

To view the discussion, visit: http://community.zenoss.org/message/62656#62656

--------------------------------------------------------------
kevinlo:

I would not use getRRDValue in these fields. It puts pressure on Zenhub which can already be a bottleneck at times. What I would suggest is to write a modeler which fetches the value you're looking to correlate with and populate a custom property, zPropery or cProperty, and read that value in to the threshold in a tales expression.

This is a much more scalable solution.

Best,
--Shane (Hackman238)
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/62656#62656]

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]