HI Dominik,

almost all that appears in discovery/* refers to CMS UI zone discovery. If you are using zones or discovery jobs in legacy UCMDB Local Client, these rest queries will return empty results (unfortunately). The R&D is pushing for more enrollment of customers in the new CMS UI admin interfaces. I think that CMS UI is still not there yet.

Petko

Hi Petko,

Indeed, it looks like all those discovery endpoints are aimed at getting info from zone based discovery.  In our setup we don't have any zone based discovery, only discovery jobs.  So this confirms that the available REST API can't be used to get insights into the discover jobs that way.  I'll be checking if JMX can help here.

R&D should focus more on getting more REST API functionalities exposed instead of focussing on CMS UI.

Off-topic but, CMS UI will never be a good replacement for local client the way it's evolving now.  I tried to use it, but it's clear there are no experienced UI designers working on the CMS UI.

Regards,

Dominik

it is even worse that if you want to enable CMS UI Zone discovery, it disables the Zones and Jobs from local client.  So the cost for moving to CMS UI is high and not possible for many of the old clients of UCMDB. 

I guess R&D is trying to make the solution more user friendly for new administrators than pleasing old users. By the way the latest CMS UI Discovery is not so bad. It is responsive, you are able to fetch the communication file and trigger the discovery for troubleshooting