Getting specific datapoints using the REST API
In this post: https://community.logicmonitor.com/archive-13/getting-datapoint-data-via-rest-api-1249 … @Sarah Terry provides information on how to get data for just specific datapoints, reducing load on the API, minimizing network traffic and reducing deserialization load on the client. While this is VERY useful, it is not currently possible to do this for graph data. An example of such a call would be: {{logicmonitor_url}}/device/devicedatasourceinstances/229505122/graphs/-1/data?datapoints=sentpkts …which brings back the default graph data (all datapoints), though this would also work for a specific graph. The advantage of this approach to data fetch is that it permits the retrieval of virtual datapoints. In order to achieve the same benefits, we (Panoramic Data) request that the same datapoint filtering is added to the {{logicmonitor_url}}/device/devicedatasourceinstances/{instanceId}/graphs/{graphId}/data endpoint. Of lesser importance would be other graph API endpoints (e.g. the website graph API endpoint) Thanks in advance! David39Views15likes0CommentsAlert Thresholds - Changing units Free Space datapoint on Volume Capacity
Hi All, I wanted to put a question to you all to see if you have any recommendations. We have several drives that we are monitoring where it doesn’t make sense to track the % used datapoint due to the very large (or in a couple of cases, very small) total capacity of the drive. As such, we configured the Free Space datapoint for alerts instead. This is working well, however because the Free Space datapoint tracks “available storage capacity of the volume in bytes” it is difficult to quickly understand the potential impact of the alert when it triggers and error for < 268435456000 bytes remaining. Is there any way to change this datapoint so that it reports in a larger unit? GB would be preferred, but even MB would be helpful.Solved98Views8likes4Comments