Get all devices in all sub device groups via LogicMonitor REST API
Hi, I am trying to use the LogicMonitor REST APIget a list of allof the devices in a given device group, including all devices in all sub groups below in the hierarchy. I have tried using the /device/groups/{id}/devices API but it just seems to return the devices in that immediate device group. This behaviour seems contrary to the /device/groups/{id}/alerts and /device/groups/{id}/sdts methods which do work with any sub groups below. This was previously possiblevia the getHosts RPC API method. I believe it is still possible but we are looking to migrate away from the RPC API. Can someone please advise on a solution for this issue?61Views0likes6CommentsAdd device to Collector with least devices in rest api
I hope someone here can help, Using powershell and the rest API I would like to do a lookup of selected collectors find which has the least amount of devices on it then add the a new device. I have the script for adding the device and that works greatjust need the collector lookup, has anyone done something similar. Thank you in advanced for all help provided PaulSolved37Views0likes49CommentsNetscan ##SYSTEMNAME##
If you choose to use a netscan and want to rename your devices to the system name using##SYSTEMNAME## the device must respond to SNMP first. The problem is LogicMonitor uses WMI exclusively for Windows, SNMP exclusively for most network equipment and vmware's api for hosts. So in my case I do not have SNMP configured everywhere. Now lets say you are scanning 5 full /24's and they put these devices in your portal. Now I am stuck having to go to the info tab on each one, locate the system.sysname(if present) and then click on Manage and rename the device. With 5 full /24's this a massive amount of devices to have to manually touch. Netscans have to be able to use the default method of connecting to each device and then##SYSTEMNAME## must come from that depending on the device it is trying to connect to. Making us rely on just SNMP is not feasible.32Views1like0CommentsBulk add devices to device Group
We have up to 500 devices that need to be added to a LM device group via the API - is it possible to do this in bulk, with a single API call, or do we need to make an API call per device to set the group? We'll also need to be able to remove multiple devices in future, so the same question applies for removal. I was hoping there may be a public 'Devices' property available on a device group, that would allow us to 'PUT' a device list to add/remove members, but I'm not able to find anything so far in the documentation. Thanks in advance, Sean27Views0likes2CommentsDevice graph data
Hi Team, I used the below link to get graph data for the device (Single Instance) . https://www.logicmonitor.com/support/rest-api-developers-guide/v1/data/get-graph-data/ Here I used the below Rest API /device/devices/{deviceID}/devicedatasources/{deviceDataSourceID}/instances/{instanceID}/graphs/{graphID}/data Here I have provided all input parameters for this URI. But I didn't get any data for it. I was getting only "No Data" for it . But that server acutally has data . outPut: "data" : [ "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data" ] }, { "colorName" : "green", "std" : "NaN", "min" : "NaN", "max" : "NaN", "avg" : "NaN", "visible" : true, "color" : "89A54E", "legend" : "Out Unicast", "type" : "Line", "useYMax" : false, "description" : "", "label" : "OUTUNICAST", "decimal" : -1, "data" : [ "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data" ] }, { "colorName" : "purple", "std" : "NaN", "min" : "NaN", "max" : "NaN", "avg" : "NaN", "visible" : true, "color" : "80699B", "legend" : "In (b/m)cast", "type" : "Line", "useYMax" : false, "description" : "", "label" : "INNONUNI", "decimal" : -1, "data" : [ "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data" ] }, { "colorName" : "maroon", "std" : "NaN", "min" : "NaN", "max" : "NaN", "avg" : "NaN", "visible" : true, "color" : "800000", "legend" : "Out (b/m)cast", "type" : "Line", "useYMax" : false, "description" : "", "label" : "OUTNONUNI", "decimal" : -1, "data" : [ "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data", "No Data" ] } ], "missingLines" : [ ], "timestamps" : [ 1555975800000, 1555976078000, 1555976378000, 1555976678000, 1555976978000, 1555977278000, 1555977578000, 1555977878000, 1555978178000, 1555978478000, 1555978778000, 1555979078000, 1555979378000, 1555979678000 ], "scopes" : [ ], "instances" : [ ] } }6Views0likes3Comments
Alert Tuning - Automatically include the datasource-defined threshold when adding custom threshold
I have an app admin who wants to suppress CPU critical alerting from 10PM to 4AM for his servers---ok, not a problem. We created a dynamic group filtering for his servers and set a custom alert threshold for the desired time without a critical threshold. The issue I'm having is for the rest of the day from 4:01 AM to 9:59 PM. This app admin does not have a good use case to suppress alerting during these hours, so the standards from the datasource should apply. But in order to get those standard alert thresholds take effect, I am finding I have to create another manual effective threshold for the remaining hours. This becomes a problem if we ever have to change the datasource-defined alert threshold. Having the datasource-defined global threshold automatically included (and linked/updated) as the lowest layer of the Effective Threshold stack would alleviate the need to track and update all of the one offs when new standards are approved.3Views0likes0CommentsMore AWS-centric options for Netscan via AWS (EC2) Method
- Token to name a device based on AWS tag - The ability to exclude devices based on region - All AWS tags should be imported/populated/inherited - Netscan should populate the system.aws.resourceid property instead of system.ec2.resourceid. The former is actually used by the default AWS_EC2 datasource. Probably moot if my third bullet is done.3Views0likes1CommentDevice Tree - More search options
I want to be able to search on the Device Group Description by using "gd:". Similar to being able to use "g:" to search on group. Other types of searching would be helpful as well, like on custom properties.. "cpn: & cpv:" for Custom Property Name & Custom Property Value, similar to filtering in the REST API.1View1like0Comments