Calling the REST API endpoint /type/typeName/instances returns all objects and it's properties, but only sends the nested objects details once and then just sends the uniqueId string.
Examples:
/type/LogicalDisk/instances returns "LogicalDisk" objects and it's properties, but for the nested "Host" object details are only included for the first "LogicalDisk" object in the response./type/DBSS_Database/instances returns "DBSS_Database" objects and it's properties, but for the nested "DBSS_Host" object details are only included for the first "DBSS_Database" object in the response.
This behavior is by design; when the /type/typeName/instances API endpoint is invoked, the references from the output will only contain instance details once per object. All other references will only contain the object ID.
The idea behind the design was to limit redundant information as much as possible. When a contained topology type instance refers back to its containing instance, then detail information about the container is returned, all subsequent references to the same containing instance will only contain the ID. This is because the ID is "known" and could be referred back to the detailed first record. This reduces redundant information in the returned data as there may be many objects that refer back to the same container object.
STATUS
Enhancement request FOG-11347 for documentation improvements has been submitted to development for consideration in a future release of Foglight.