Forum Discussion
I'll be getting postman running tomorrow... my time was up and had to move to another effort. Thank you for pointing the tool out to me. It looks really useful. and thanks for poking at my code. I'll verify I have the right IDs for each of those pieces as well. (Funny Note... I typed this up yesterday and didn't hit submit). I've verified that I have the right pieces and parts. You're examining the JSON in your examples... I use Powershell ISE and explore the return data using the variables. I have verified that I'm using the deviceDataSource rather than the dataSource:
PS C:\Users\cole.mcdonald> $inst_CPU
id : 8976881
dataSourceId : 5725412
deviceDataSourceId : 427972
groupId : 538636
groupName : @default
name : Perfmon_CPU-_Total
displayName : _Total
description :
lockDescription : False
deviceId : 5378
and my call was:
/device/devices/5378/devicedatasources/427972/instances/8976881/data
(I switched devices to verify that it wasn't just empty) I've tried grabbing data from both the instance directly as well as the graph data. I'm going to dig into postman... but looking at it, I don't know that it will necessarily show me anything different than I'm getting using straight powershell... and I generally dislike GUI'd applications for this sort of thing as I find them horribly inefficient (I'm old and grew up on CLI).
Here's my Postman return:
{
"dataSourceName": "Perfmon_CPU",
"dataPoints": [
"PercentProcessorTimeCounter",
"PercentProcessorTime"
],
"values": [],
"time": [],
"nextPageParams": ""
}
So it looks like it's succeeding in the call, just no data returned. Odd, because the graph shows that there should be historical data there to grab.
Related Content
- 3 months ago
- 2 years ago
- 4 months ago