Locked
Discussion interactions are currently paused.
Getting Datapoint data via REST API
I've been trying to get data for individual datapoints within a single instance datasource via the REST API, in this case there are ~twenty datapoints and I only want data for one of them. Using get_data: https://www.logicmonitor.com/support/rest-api-developers-guide/data/get-data/ I can pick out my datasource, however I can't find any information on filtering by datapoint. When I get data, the datapoints are all listed in an array, then the data is presented as an array of arrays for the last hour...I could get the position of the datapoint in the first array, then pick out the data using that position for each array listed in the data but that feels like a bad road to travel. query is essentially: "resourcePath = '/device/devices/73023/devicedatasources/1573061/instances/1928726/data'"
Right now I'm adding the datapoints I want to a custom graph, I can then pull out the data for that custom graph e.g. "resourcePath = '/device/devices/73023/devicedatasources/1573061/instances/1928726/graphs/3133/data'" (with multiple lines I can pick specific data by checking the line label). Although this works fine, it still feel like an additional step.
What I'd really like is:
"resourcePath = '/device/devices/73023/devicedatasources/1573061/instances/1928726/ [datapoint/datapointID] /data'"
but I can't see an ID for datapoints or an option for putting a 'name' in.
Have I missed something?
Does anyone already do this in a simple way?
Matt_Gauthier
·8 years agoI raised this issue with Support last week, as well - hadn't seen this post until just now. Ticket 87499, for reference.
Datapoint filtering doesn't appear to be working in REST API calls with a query parameter like this
?datapoints=datapoint1,datapoint5
This just results in the first two datapoints in the datasource being returned, rather than the 1st and the 5th.
Sarah_Terry
·8 years agoOkay, I see - and I am able to replicate the issue. It appears to be a bug with the current implementation, sorry about that - we'll get that fixed with the next release!
Tom_S-L
OP8 years agoSure... e.g.
resourcePath = '/device/devices/73023/devicedatasources/1573061/instances/1928726/data'
Two alternative queries:
queryParams = '?datapoints=requests_queue_depth_priority_higher'
queryParams = '?datapoints=requests_sent_to_team_last_day'
Results - note the data is identical, also, "requests_queue_depth_priority_higher" should be a list of integers as per attached image:
Response Status: 200
Response Body: {
"status" : 200,
"errmsg" : "OK",
"data" : {
"dataSourceName" : "[can't say sorry]",
"dataPoints" : [ "requests_queue_depth_priority_higher" ],
"values" : [ [ 0.0249 ], [ 0.0337 ], [ 0.0155 ], [ 0.044 ], [ 0.0476 ], [ 0.0817 ], [ 0.0646 ], [ 0.0589 ], [ 0.0201 ], [ 0.0686 ], [ 0.0589 ], [ 0.0713 ], [ 0.0926 ], [ 0.0354 ], [ 0.034 ], [ 0.0418 ], [ 0.0785 ], [ 0.06 ], [ 0.0434 ], [ 0.0998 ], [ 0.1075 ], [ 0.0537 ], [ 0.0934 ], [ 0.0964 ], [ 0.1088 ], [ 0.1086 ], [ 0.1251 ], [ 0.1058 ], [ 0.0316 ], [ 0.0932 ] ],
"time" : [ 1504198000000, 1504197880000, 1504197760000, 1504197640000, 1504197520000, 1504197400000, 1504197280000, 1504197160000, 1504197040000, 1504196920000, 1504196800000, 1504196680000, 1504196560000, 1504196440000, 1504196320000, 1504196200000, 1504196080000, 1504195960000, 1504195840000, 1504195720000, 1504195600000, 1504195480000, 1504195360000, 1504195240000, 1504195120000, 1504195000000, 1504194880000, 1504194760000, 1504194640000, 1504194520000 ]
},
"nextPageParams" : ""
}
Response Status: 200
Response Body: {
"status" : 200,
"errmsg" : "OK",
"data" : {
"dataSourceName" : "[can't say sorry]",
"dataPoints" : [ "requests_sent_to_team_last_day" ],
"values" : [ [ 0.0249 ], [ 0.0337 ], [ 0.0155 ], [ 0.044 ], [ 0.0476 ], [ 0.0817 ], [ 0.0646 ], [ 0.0589 ], [ 0.0201 ], [ 0.0686 ], [ 0.0589 ], [ 0.0713 ], [ 0.0926 ], [ 0.0354 ], [ 0.034 ], [ 0.0418 ], [ 0.0785 ], [ 0.06 ], [ 0.0434 ], [ 0.0998 ], [ 0.1075 ], [ 0.0537 ], [ 0.0934 ], [ 0.0964 ], [ 0.1088 ], [ 0.1086 ], [ 0.1251 ], [ 0.1058 ], [ 0.0316 ], [ 0.0932 ] ],
"time" : [ 1504198000000, 1504197880000, 1504197760000, 1504197640000, 1504197520000, 1504197400000, 1504197280000, 1504197160000, 1504197040000, 1504196920000, 1504196800000, 1504196680000, 1504196560000, 1504196440000, 1504196320000, 1504196200000, 1504196080000, 1504195960000, 1504195840000, 1504195720000, 1504195600000, 1504195480000, 1504195360000, 1504195240000, 1504195120000, 1504195000000, 1504194880000, 1504194760000, 1504194640000, 1504194520000 ]
},
"nextPageParams" : ""
}
Sarah_Terry
·8 years agoHi Tom - If you can share the details of your specific request here, I can take a look. Thanks!
Tom_S-L
OP8 years agoHi Sarah,
Thank you for getting this pushed through so quickly - the Datapoint Filter shows me a reduced set of data which is a good start...unfortunately, it doesn't matter which datapoint I filter on, I always get the same data back even though "dataPoints" : [ "my_data_point" ], shows correctly in the result.
Should I raise this with LM support?
Thanks,
Tom.
Tom_Lasswell
·8 years agoI thought I had posted at one time (but obviously didn't), here's a PowerShell script that parses through the data that's returned so that you can have a good object to work with. Can see what's done here to possibly work in whatever language you want to program in.
there's some work that I haven't finished on this (mainly if it doesn't include an instance ID), but thanks @Sarah Terry for the additional rest path as well, I'll be using that to narrow this function even more!
Mosh
·8 years ago@Sarah Terry Actually using start and end timestamps does the job for me, thanks.
Sarah_Terry
·8 years agoYou can now specify a datapoints query parameter to limit the data returned in the request, like this: GET /device/devices/{id}/devicedatasources/{id}/instances/{id}/data?datapoints=datapoint1,datapoint5. Does that satisfy both of your use cases?
Documentation updated here: https://www.logicmonitor.com/support/rest-api-developers-guide/data/get-data/
@Mosh you should be able to already filter by epoch using the start and end parameters - is that what you meant by datapoint timestamp?
Mosh
·8 years agoI'd like this too please, though I'd prefer to do it by DataPoint timestamp (epoch), which I think you already store in the history.
Tom_S-L
OP9 years agoGreat, thanks Sarah.
Sarah_Terry
·9 years agoHi Tom,
Thanks for posting - we should be able to add in a sub-resource for data specific to one datapoint, or at least offer a query parameter that restricts the datapoints data is returned for. I'll get the ball rolling on that.
Thanks,
Sarah