Network Interface Utilization on Windows Servers

This support forum board is for support questions relating to Nagios XI, our flagship commercial network monitoring solution.
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Network Interface Utilization on Windows Servers

Post by lmiltchev »

Go to Home->Service Detail-><your service>->Configure->Re-configure this service, and see if you have the same command as the one you used successfully from the CLI. You are correct about the "Test Check Command" escaping issues under the CCM. Testing commands from the CCM works most of the time but not always, because of the escaping issues. Try modifying the command in the "Monitor the service with this command..." text box, click on "Update" and and schedule an immediate check. Hope this helps.
Be sure to check out our Knowledgebase for helpful articles and solutions!
joe.ward
Posts: 44
Joined: Tue Aug 06, 2013 10:44 am

Re: Network Interface Utilization on Windows Servers

Post by joe.ward »

Go to Home->Service Detail-><your service>->Configure->Re-configure this service says the service is configured through CCM so I have to go there.

Where is the "Monitor the service with this command..." text box? The only place I see to set up the command is in CCM.
slansing
Posts: 7698
Joined: Mon Apr 23, 2012 4:28 pm
Location: Travelling through time and space...

Re: Network Interface Utilization on Windows Servers

Post by slansing »

Okay,

In the CCM page for this service change the counter value to:

Code: Select all

"\\Network Interface\\(Intel\\[R\\] PRO_1000 MT Network Connection\\)\\Bytes Sent/sec"
joe.ward
Posts: 44
Joined: Tue Aug 06, 2013 10:44 am

Re: Network Interface Utilization on Windows Servers

Post by joe.ward »

Well, after exhausting all other options, I found that just the straight text, escaping the \'s did the trick. Sure thought we'd tried that before...

"\\Network Interface(Intel[R] PRO_1000 MT Network Connection)\\Bytes Sent/sec"

works from the Core Config service definition page!

I tried to set the label using ""\\Network Interface(Intel[R] PRO_1000 MT Network Connection)\\Bytes Sent/sec","Bytes/sec" and now all that is displayed in the results is "Bytes/sec". Even when I go back and remove ",Bytes/sec" from the definition, it still shows as the returned value. How do I clear the label/format and go back to the basic, unformatted, result?
yancy
Posts: 523
Joined: Thu Oct 06, 2011 10:12 am

Re: Network Interface Utilization on Windows Servers

Post by yancy »

What label are you speaking of? I'm not seeing any field titled label in the CCM...

-Yancy
joe.ward
Posts: 44
Joined: Tue Aug 06, 2013 10:44 am

Re: Network Interface Utilization on Windows Servers

Post by joe.ward »

Hello Yancy

I've hit this problem again :cry:

check_nt -v COUNTER takes "-l <param1>,<param2>" where param2 is the "label".

"\\Network Interface(Intel[R] PRO_1000 MT Network Connection)\\Bytes Sent/sec","Windows Performance Counter - Bytes/sec %.0f" sets the label on Service Status Detail - Performance Graph to Windows Performance Counter - Bytes/sec %.0f. If I shorten param2 to Bytes/sec %.0f, the Performance Graph still shows the previous label. Flushing the browser cache, logging out of Nagios, even restarting the Performance Grapher process does not sync the labels up.

Service Status Details - Overview shows the last returned value is "Bytes/sec 136739" (looks like the correct label).

Why doesn't Performance Graph use the same label as Overview does? Performance Graph even shows it with %.0f as a text string (expected this format output string to be suppressed in the graph legend). "%.0f" should be replaced by the value. How can I get them into sync?
User avatar
lmiltchev
Bugs find me
Posts: 13589
Joined: Mon May 23, 2011 12:15 pm

Re: Network Interface Utilization on Windows Servers

Post by lmiltchev »

I was able to recreate the issue. We will do some digging into it to determine if this is a bug, and will get back to you.
Be sure to check out our Knowledgebase for helpful articles and solutions!
Locked