1. How to get more info on a network outbound spike using Zenoss

I'm new to Zenoss and been assigned to find some hints on a big spike in one of our Node.JS / HAProxy stacks. The server is usually busy but on arbitrary timeframes it starts to send enormous amount of messages. Like it has an average outbound of 15Mbps and suddenly goes up to 60Mbps and then goes back to normal.We are providing a real-time service and this spike is creating some lag which is essential to us (It is an stock exchange application, designed for a specific broker) Using Zenoss, I want to get more information out of this issue.

First, I need to make Zenoss get faster responses from SNMP. In the current situation, it draws the point on the graph every 5 minutes for network outbound, so I just have a vague idea of how long does the spike take. How can I make this more accurate?

Second, I am looking into NodeJS monitoring applicability in Zenoss. Are there options in Zenoss to monitor NodeJS itself? Or should I find some other way doing this?

Any help and ideas would be really appreciated, as I am a bit stuck here.

2. RE: How to get more info on a network outbound spike using Zenoss

For a test node, select its Configuration Properties and find the zSnmpCollectionInterval attribute. The default is 300 (seconds). I wouldn't go to less than 60 seconds.

Depending on your versions of Zenoss, you may need to delete (or at least "hide") the current collected data - this is true for any version of Zenoss at V4 or less. I think if you have Zenoss 5 or 6 there is no need to delete the existing data. If you have V4 or less and don't know how to clear a performance data file, come back to us here.

Original Message:Sent: 12-16-2018 05:16 AMFrom: Amir KhosrowshahiSubject: How to get more info on a network outbound spike using Zenoss

I'm new to Zenoss and been assigned to find some hints on a big spike in one of our Node.JS / HAProxy stacks. The server is usually busy but on arbitrary timeframes it starts to send enormous amount of messages. Like it has an average outbound of 15Mbps and suddenly goes up to 60Mbps and then goes back to normal.We are providing a real-time service and this spike is creating some lag which is essential to us (It is an stock exchange application, designed for a specific broker) Using Zenoss, I want to get more information out of this issue.

First, I need to make Zenoss get faster responses from SNMP. In the current situation, it draws the point on the graph every 5 minutes for network outbound, so I just have a vague idea of how long does the spike take. How can I make this more accurate?

Second, I am looking into NodeJS monitoring applicability in Zenoss. Are there options in Zenoss to monitor NodeJS itself? Or should I find some other way doing this?

Any help and ideas would be really appreciated, as I am a bit stuck here.

3. RE: How to get more info on a network outbound spike using Zenoss

Thanks Jane, I edited the interval and now I'm getting some better results. By the way, we are using Zenoss Community Edition (Core) ver. 5.1.2. And the issue you mentioned did not happen (the graph just continued to give data points in 1 minute intervals). There is only one thing left for me to ask: I've looked inside the available monitoring packages and could not find anything related to Node.JS. Is there anything I can look into?

Original Message:Sent: 12-16-2018 12:09 PMFrom: Jane CurrySubject: How to get more info on a network outbound spike using Zenoss

What version of Zenoss are you running here?

For a test node, select its Configuration Properties and find the zSnmpCollectionInterval attribute. The default is 300 (seconds). I wouldn't go to less than 60 seconds.

Depending on your versions of Zenoss, you may need to delete (or at least "hide") the current collected data - this is true for any version of Zenoss at V4 or less. I think if you have Zenoss 5 or 6 there is no need to delete the existing data. If you have V4 or less and don't know how to clear a performance data file, come back to us here.

Original Message:Sent: 12-16-2018 05:16 AMFrom: Amir KhosrowshahiSubject: How to get more info on a network outbound spike using Zenoss

I'm new to Zenoss and been assigned to find some hints on a big spike in one of our Node.JS / HAProxy stacks. The server is usually busy but on arbitrary timeframes it starts to send enormous amount of messages. Like it has an average outbound of 15Mbps and suddenly goes up to 60Mbps and then goes back to normal.We are providing a real-time service and this spike is creating some lag which is essential to us (It is an stock exchange application, designed for a specific broker) Using Zenoss, I want to get more information out of this issue.

First, I need to make Zenoss get faster responses from SNMP. In the current situation, it draws the point on the graph every 5 minutes for network outbound, so I just have a vague idea of how long does the spike take. How can I make this more accurate?

Second, I am looking into NodeJS monitoring applicability in Zenoss. Are there options in Zenoss to monitor NodeJS itself? Or should I find some other way doing this?

Any help and ideas would be really appreciated, as I am a bit stuck here.

4. RE: How to get more info on a network outbound spike using Zenoss

I also don't see any ZenPacks around for Node.JS. There seems to be one for RaphaelJS (https://www.zenoss.com/product/zenpacks/raphaeljs ) which might give you some ideas if you want to write your own ZenPack. Alternatively, can you construct something using a COMMAND template. Depends very much on what you want to do - and I'm afraid I am no Javascript guru and have never used Node.JS :(

Original Message:Sent: 12-17-2018 02:07 AMFrom: Amir KhosrowshahiSubject: How to get more info on a network outbound spike using Zenoss

Thanks Jane, I edited the interval and now I'm getting some better results. By the way, we are using Zenoss Community Edition (Core) ver. 5.1.2. And the issue you mentioned did not happen (the graph just continued to give data points in 1 minute intervals). There is only one thing left for me to ask: I've looked inside the available monitoring packages and could not find anything related to Node.JS. Is there anything I can look into?

------------------------------Amir KhosrowshahiSystem Administrator

Original Message:Sent: 12-16-2018 12:09 PMFrom: Jane CurrySubject: How to get more info on a network outbound spike using Zenoss

What version of Zenoss are you running here?

For a test node, select its Configuration Properties and find the zSnmpCollectionInterval attribute. The default is 300 (seconds). I wouldn't go to less than 60 seconds.

Depending on your versions of Zenoss, you may need to delete (or at least "hide") the current collected data - this is true for any version of Zenoss at V4 or less. I think if you have Zenoss 5 or 6 there is no need to delete the existing data. If you have V4 or less and don't know how to clear a performance data file, come back to us here.

Original Message:Sent: 12-16-2018 05:16 AMFrom: Amir KhosrowshahiSubject: How to get more info on a network outbound spike using Zenoss

I'm new to Zenoss and been assigned to find some hints on a big spike in one of our Node.JS / HAProxy stacks. The server is usually busy but on arbitrary timeframes it starts to send enormous amount of messages. Like it has an average outbound of 15Mbps and suddenly goes up to 60Mbps and then goes back to normal.We are providing a real-time service and this spike is creating some lag which is essential to us (It is an stock exchange application, designed for a specific broker) Using Zenoss, I want to get more information out of this issue.

First, I need to make Zenoss get faster responses from SNMP. In the current situation, it draws the point on the graph every 5 minutes for network outbound, so I just have a vague idea of how long does the spike take. How can I make this more accurate?

Second, I am looking into NodeJS monitoring applicability in Zenoss. Are there options in Zenoss to monitor NodeJS itself? Or should I find some other way doing this?

Any help and ideas would be really appreciated, as I am a bit stuck here.