New Metrics Component not showing NRPE services

[WillemDH]

Hello,

I'm testing the new Metrics component and it seems it doesn't find my Windows NRPE based services. So as an example, I have a bunch of 'DRV_X_Load' named services, one for each disk. I would have expected that the new Metrics component would be able to compare the data of these disk loads? It only finds my check_nt based services. As I'm not using any check_nt checks on my production servers, this is rather useless.

Please let me know how I can make the new Metrics component pick up these services? This is only on my test environment. As I'm using custom naming conventions for all my checks, I fear none of them will show up on my production server.

A list of the naming conventions I'm using for checks that should be visible in the Metrics component.. (These are just a few of many) I prefer grouping services with a prefix.

DRV_X_Usage => For all Disk usage checks
DRV_X_Load => For all Disk load checks
NET_Connections => Network connections
NET_Load => Network IO
SRV_CPU => CPU Statistics
SRV_Memory => Memory info
SRV_Ping => Ping

Any help to get this working somehow is welcome, as at this moment, the new Metrics component is doing nothing..

Willem

[lgroschen]

Willem,

The new component is pulling in data based on hard coded command names and service names. This tracker topic that you started originally has the format that work with them now that I posted as the last comment. I also added a task internally so that we can add custom commands and services into the component so you can add them at will, so that will be an additional feature for another 5 release.

http://tracker.nagios.com/view.php?id=471

[WillemDH]

Really? Kind of disappointing...

And I indeed also use custom commands..

Please let me know if you want any more details.

It would have been nice if someone had asked for some input on this or let me test this.

An why is this feature request closed then? It hasn't solved anything at the moment and I've only been waiting for something like this since 2013-11-26 17:29.

[lgroschen]

Well that's the problem from the beginning is that users will have many different types of commands and services that we would need to account for a large amount of them. It was closed because the component was updated, but as I said internally we have a task to make it more customizable. An update wouldn't be difficult and it would mostly just involve changing the utils-metrics.inc.php file in XI itself.

I'll talk to the other devs about this and maybe we can just open a new task in tracker and have it prioritized since you have been waiting on it. I can always try!

[WillemDH]

Luke,

No offense, and sorry for the short reaction. But I had to deal with a non-working Metrics component since I started using XI. Polluting the old XI view, creating numerous questions from my users /boss who didn't got it to work etc etc. And now you did release something as a result of a fr I made and it still does not work.

OK, going to stop complaining.. (need some sleep)

I'll talk to the other devs about this and maybe we can just open a new task in tracker and have it prioritized since you have been waiting on it. I can always try!

Yes, I would like that. And please oh please let me know if I can help / test or provide any info. The naming conventions I'm using for services and commands are really no rocket science, so it might be a small change to get it working. I had a short look into /usr/local/nagiosxi/html/includes/utils-metrics.inc.php

Grtz

Willem

[lgroschen]

Willem,

No offense taken at all. I know for sure that it won't be that difficult to update and we will look to you to test it in the future.

For now you can easily add your updates in and I'll give you a hand with the changes if you want to email the entire list of services and the check commands they are run through - PM or email is fine.

[WillemDH]

Sent you an email with extra info. Thanks for looking into this.

[jdalrymple]

It would have been nice if someone had asked for some input on this or let me test this.

We did things a bit differently in that we did ship the beta. That said we still recognize we have work to do on the release process. The good news as lgroschen indicated is that it's just a component so we can tune it up and get it out pretty easy.

And now you did release something as a result of a fr I made and it still does not work.

The changes made weren't geared towards any single feature request (it may have been 1 feature request ID in our system) but rather an outpouring of requests that other types of checks work. For the vast majority of those requests just working with wizard generated services was fully adequate. Not to say that we don't take your requests seriously, but the changes in this case weren't for any 1 person.

Nonetheless you have the right person on the case, and since it's now being handled outside of the thread is it OK if I lock it?

[WillemDH]

Please lock. Tx