Regarding CPU and Memory and Disk Performance Data Collection for multiple servers

Yeah, I'm using the ID of each bit exclusively.  I figured we need the instance IDs as they apply to the specific resource rather than the id of the DS itself... which would be the same for every instance of that DS as applied to any resource.  I've built quite a few Relational DB driven apps   I've spent my time chasing IDs... and then banging my head against my desk once the "obvious" problem was unconvered.

The instance shows the deviceID, the deviceDataSourceID, and the instanceIDs as their own properties in the returned JSON (here parsed into a PSObject).  that dds ID should be the specific ID of the DS as applied to that device.  Everything seems to be correct on the walk up to the "/data"  I'm a little surprised we can't just get "/instance/#####/data" from it as a direct access to the endpoint of the walk since it's a unique ID for the instance itself.  Overly complicated data access method that is prone to error and misinterpretation.