Which properties can be on a Resource Group Inventory Report?
I made a Resource Group Inventory targetingCustomers/!(*/*) to get the host counts for each customer folder, using the convenient built-in or default property host.count, but I would like to put other information about each group as columns. But the only options that are suggested are system.categories and system.deviceGroupId …. which is weird, and not particularly. But I just forced in columns named name, description, system,displayname, anything I could think of, and those columns all end up blank. Is there any documentation on what properties work on this report? Or am I missing something obvious? Thanks!Solved93Views11likes1CommentDynamic groups formatting question
Hi all, I’m new to the product and trying to figure out the basics of how it wants things formatted. I’m trying to setupa simple Dynamic group with 2 variables and can’t figure out how it wants it formatted to combine them. I just want the custom query to contain the following. system.displayname=~"test" device_type=~"server"Solved219Views8likes2CommentsUIv4 - Managing Static Group Memberships - Huge UX Issue?
Hey y’all, I amentirelyunable to intuitout how I can move resources into a static group in UIv4 -- The closest I’ve been able to get to documentation for this are: Resource Group Overview (New UI) | LogicMonitor Changing Resource Group Membership (New UI) | LogicMonitor The last link seems to indicate controlling this on a per-Resource basis -- but Ishouldbe able to add multiples devices to a group from the group’s perspective from a usability perspective. Am I missing something completely obvious here? Mostly asking because this is the first real thing that’s severely underservedmy intuition with UIv4 -- hoping this will also elevate visibility, as I tend to bereallystrong on intuition, and LogicMonitor has suited my intuitionvery well historically.85Views6likes10CommentsIs there a link between Active Directory security groups and Security groups in LogicMonitor?
Are we able to sync Security groups in LogicMonitor with security groups in Active Directory? This is our preferred way of managing group access in third party solutions if at all possible. Ideally, I would like to add a user to an AD security group, and then LogicMonitor would sync that group and add them into the relevant LogicMonitor security group. This would massively improve the manageability of LogicMonitor for us, and improve security. If this is not possible natively, is there API level access to LogicMonitor and could we for example have a script that scrapes certain group memberships and then pipes that data into LogicMonitor?127Views1like4Comments
Random custom properties appearing within our 'root' folder
Hello to everyone, For the past couple of weeks we've been noticing that from time to time 'customProperties' get created within our 'root' group at LM. We've asked our team if anyone created those, everyone stated that they weren't manually created. Tried to check it within Audit logs, but I can't find any event that relatesto that action. I'm not sure what is causing this (couldn't be LM fault)... Examples of properties that get created: - snmp.community - esx.user/pass We've a bunch of folksworking on this at the same time & we're not discarding the possibility of this being done by mistake (however, the weird thing is we can't see this in the Audit logs). Anyone faced this sort of scenario in the past? Thank you!Solved24Views1like4Comments
Alert clustering based on matching datasource instances across grouped devices
I have a device group that has the same datasource applied. This datasource auto-discovers and will spin up matching instances across all devices in the group. I would like to have clustered alerts based on the matched instances across all devices in the group. For example, (pardon the ASCII-like visualization) ClusterGroup |__ Device1 | |__ DatasourceA | |_ Instance_ABC | |_ Datapoint_I | |_ Datapoint_II | |_ Instance_DEF | |_ Datapoint_I | |_ Datapoint_II | |_ Instance_GHI | |_ Datapoint_I | |_ Datapoint_II |__ Device2 | |__ DatasourceA | |_ Instance_ABC | |_ Datapoint_I | |_ Datapoint_II | |_ Instance_DEF | |_ Datapoint_I | |_ Datapoint_II | |_ Instance_GHI | |_ Datapoint_I | |_ Datapoint_II |__ Device3 |__ DatasourceA |_ Instance_ABC |_ Datapoint_I |_ Datapoint_II |_ Instance_DEF |_ Datapoint_I |_ Datapoint_II |_ Instance_GHI |_ Datapoint_I |_ Datapoint_II If Instance_ABC's Datapoint_I is alerting at the specified cluster threshold in my hypothetical group, I want to generate a cluster alert. If some time afterwards, the situation in my environment gets worse and Instance_GHI's Datapoint_II is alerting at the specified cluster threshold, I want another cluster alert for that instance-datapoint as well.10Views0likes1CommentCollector dynamic groups
Collector groups were added recently, and are detailed here:a href="https://communities.logicmonitor.com/topic/637-collectors" rel="">https://communities.logicmonitor.com/topic/637-collectors Now let's expand upon that functionality...What ifcollectors be grouped dynamically? Identically to how Devices dynamic groups work,could I assign properties to collectors, then build dynamic groups based from the properties? Ways thatenvision sorting collectors: Production/test, primary/backup,collector number (1-99, 100-199, 200-299, etc.),zip code, time zone, alphabetical. In each of these cases, this would give full flexibility on how collector upgrades are scheduled. Currently if we have a mass collector upgrade to a new General Release, it can be a little painful to manage so many upgrades running simultaneously (or at least in very short order). I am most interested in being able to split them up into primary, backup and single collector groups. This way, I know that it's pretty safe to upgrade the collectors that have backups after hours, since there is another collector to failover to. And I surely want to be available staff-wise if I am doingupgrades for those collectors that have no backup collector. Close behind sorting into primary/backup/singleis the need to sort them by customer (which currently works fine). The issue is that you can't put a collector into more than one group, which precludes from even setting up these to items manually.4Views1like1Comment
Permissions for Datasource, Alert, and Escalation Chain Groups
As we move towards a DevOps model, we increasingly have a need for small teams to have full admin access to the tools they use to manage their IT services. When it comes to LogicMonitor, this has proven difficult with the existing role permission model. DevOps pods would like to be able to manage their own datasources, alerts, and escalation chains but this isn't possible unless we give them broad access rights to those areas, which could cause significant harm to other groups of monitoring users. For example, an inexperienced DevOps user could inadvertently modify a datasource that applies to all Windows devices or they could create an alert rule that causes alerts not to be delivered to other users. To solve this problem, I'd propose that LogicMonitor offer alert groups, escalation chain groups, along with the existing datasource groups. Then, LogicMonitor could provide the ability to restrict roles to manage these specific groups. DevOps pods could be given the ability to manage their own custom subset of datasources and set up their own alerts in a rule range after the main set of rules.5Views4likes1Comment"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.1View0likes0CommentsCustom Alert-Groups for SDT
When we reboot a Server or a Application Set our NOC does not know all the Devices, Instances and/or services impacted so we get flooded with alerts for a known event. Example: I need to reboot device WebServer-xyz - TheServer, the Switch ports, Storage Sessions and HTTP/S Service are all monitoredin LM Like to be able to SDT just these items with one SDT, and not entire switches or devices. So be able to create an "Alert-Group"ie "WebServer-xyz" where you can then add Instances from multiple devices, entire device, Service, Instance Groups, Device Group aka any defined in LM. Then just Add one SDT to the Alert-Group aka one-stop-shopping.10Views0likes1Comment
UIv4 - Managing Static Group Memberships - Huge UX Issue?
Hey y’all, I amentirelyunable to intuitout how I can move resources into a static group in UIv4 -- The closest I’ve been able to get to documentation for this are: Resource Group Overview (New UI) | LogicMonitor Changing Resource Group Membership (New UI) | LogicMonitor The last link seems to indicate controlling this on a per-Resource basis -- but Ishouldbe able to add multiples devices to a group from the group’s perspective from a usability perspective. Am I missing something completely obvious here? Mostly asking because this is the first real thing that’s severely underservedmy intuition with UIv4 -- hoping this will also elevate visibility, as I tend to bereallystrong on intuition, and LogicMonitor has suited my intuitionvery well historically.Is there a link between Active Directory security groups and Security groups in LogicMonitor?
Are we able to sync Security groups in LogicMonitor with security groups in Active Directory? This is our preferred way of managing group access in third party solutions if at all possible. Ideally, I would like to add a user to an AD security group, and then LogicMonitor would sync that group and add them into the relevant LogicMonitor security group. This would massively improve the manageability of LogicMonitor for us, and improve security. If this is not possible natively, is there API level access to LogicMonitor and could we for example have a script that scrapes certain group memberships and then pipes that data into LogicMonitor?