Ability to exclude a device(s)/device groups from a Dashboard widget?
Hi, I am fairly new to LogicMonitor and this is my first time using the community, so forgive me if this has already been asked/answered somewhere.. but is there a way that you can exclude specific devices/device groups from a widget within a dashboard? As an example, I don’t want our File Servers to appear on our Volume Utilization widget as each of the disks will always be operating at 90%+ utilization, so I’d like to at least have to option to exclude them as “known exceptions” if you like. I couldn’t see any logical settings within the widget itself which I could amend to configure this, and I alsoreported this to customer support team who said that there isn’t currently a global expression which could be applied to the widget in order match our requirement. Does anyone know whether I’m missing a trick here or whether this has is on the LogicMonitor roadmap for the future? Thanks in advance!200Views6likes3CommentsGet 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?61Views0likes6CommentsWas a drag and drop block or confirmation prompt ever added for resource folders?
We had an incident recently where someone accidentally moved a folder in the UI but didn’t realize it. Thankfully it was caught somewhat quickly, and it was over holiday. so nobody noticed. We already have our roles tuned and people limited on access but we are all human. I found a 4 year old and a 7 year old post here asking about this. But was there ever a pin or property or setting that was ever developed to put a bit of safety on accidental resource group moves? I looked around on the manage options but I didn’t find anything. I’m planning to write a script that checks the most important folders once an hour or so, by both name/path and by the underlying ID, so that we can get an alert if this happens. I’m wondering if anything was ever done? Or if any users here have come up with solutions? I plan to make a product request in the UI if it hasn’t been implemented. Thanks!39Views7likes3CommentsBulk 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, Sean27Views0likes2Comments"Sticky" Device Group handling for dashboards and alerts
One of the biggest frustrations for us with LogicMonitor is breaking a bunch of dashboards and alerts if we move device groups to another location in the overall device group tree. For example: Say we have a nested device group called "Infrastructure/Hosts". Now our environment has changed a bit, and we want to add better organization to support the new changes to our environment. We move the hosts group to the following location "Infrastructure/PhysicalDevices/Hosts". All alert rules and dashboards that were filtering on "Infrastructure/Hosts" have now been broken, even though the devices in the group need the same alerting and dashboards. Now we have to go through and fix each Alert Rule and Dashboard Widget that used "Infrastructure/Hosts" to now point to "Infrastructure/PhysicalDevices/Hosts". As you can imagine, as environments scale up and evolve, subgroups are going to be moved around all the time. Redoing dashboards and alerts every time this happens adds a tremendous amount of labor, and can lead to people missing changes, leaving behind broken alerts or dashboards that you may not find out about until an emergency has already happened. What we're proposing: "Sticky" device group handling - If a group or subgroup used in an Alert Rule or Dashboard changes location, this location should automatically be updated and reflected in the dashboard. This is how most modern applications handle this sort of thing anyway, and it's a huge time saver. Given the critical nature of this tool's function, this would go along way towards preventing accidentally breaking monitoring that companies rely on to keep their environments running.1View0likes0Comments