Nagios Support Forum

I would like to request that for the timestamps in this function, rather than forcing us to translate between unix epoch timestamps and human time, that perhaps something that is still an integer and better for the people writing the code be used, such as: 20190326095200 still an integer. But easier...

it'd be okay, but not necessary. As long as I can add/delete AD users, that's fine.

what is needed desperately is the ability to modify existing objects, i.e. user permissions, services, hosts, hostgroups, etc. that's far more of a need than browsing AD I think.

I think I was being imprecise. In the Web UI, I have to have an AD account that allows me to see the users I want to add, and a password for that, so I can browse the AD tree and select users. That's the user name I'm referring to, not the user name of the AD user I am trying to add.

So looking at updating my Nagios REST API front end to allow for the 5.5.x changes, and I have a question about adding users that are in AD. When doing so via the Web UI, you have to enter in a valid AD user name and password. But looking in the API docs, all I see is a user name. Is that correct? B...

okay, another one. I notice in Fusion that I can add AD/LDAP users, but when I go to look in the help for REST APIs in Nagios XI 5.5.2, there's no documentation/help for adding users at all. Is this going to be changed soon?

GET Objects/Service is showing the objects (whatever core sees), not the configuration. Basically, if you added a service to let's say 100 hosts, you would see it as a "separate" service (object) under each and every one of these hosts. Right, but that's not how you view it in CCM. In CCM...

I was going through this when I realized that if I have the same service attached to 50 hosts, it gets 50 separate entries in the return for GET Objects/Service, and each entry is treated like a completely separate service. This creates a huge amount of work if one wants to get, say a list of servic...

If this was intentional, then please pay more attention to documenting this kind of thing. If this was not, then it's a rather large bug. I just had a word from our developers, who confirmed that this change was intentional. The documentation will be updated in 5.5.2, which should be coming out soo...

and objects/hostgroup

This also happens with objects/contact