Dynamic 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 setup a 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"Solved337Views8likes2CommentsIs 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?152Views1like4CommentsWhich properties can be on a Resource Group Inventory Report?
I made a Resource Group Inventory targeting Customers/!(*/*) 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!Solved126Views11likes1CommentUIv4 - Managing Static Group Memberships - Huge UX Issue?
Hey y’all, I am entirely unable to intuit out 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 I should be 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 underserved my intuition with UIv4 -- hoping this will also elevate visibility, as I tend to be really strong on intuition, and LogicMonitor has suited my intuition very well historically.99Views6likes10CommentsRandom 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 relates to 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 folks working 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!Solved36Views1like4CommentsAlert 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.19Views0likes1CommentPermissions 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.12Views4likes1CommentCustom 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 - The Server, the Switch ports, Storage Sessions and HTTP/S Service are all monitored in 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.12Views0likes1CommentGather and store more relevant WMI data for auto-grouping and category population
During the initial and periodic device auto-discovery tasks, there should be far more information stored about each device. This information should be easily accessible from the device information page and populated with data such as "Installed Programs", "Installed Features", "Running Services", "Domain Role", etc. This information could then be used to auto-group devices. For example, I should be able to create an auto-discover rule that automatically grabs all Domain Controllers based on the system.installedservices and system.installedfeatures categories. There is no reason I should have to manually move this server that is clearly a Domain Controller into my group labeled "Domain Controllers". This approach would allow administrators to "set it and forget it" instead of having to be hands-on every time a new device is added or discovered. This data can be easily populated from standard WMI classes: system.installedservices = win32_services.displayname system.serverfeatures = win32_serverfeature.Name Please help me organize my devices automatically. We have too many machines in too many environments to manually sort them all into groups.11Views0likes3CommentsEnhance UI to control which Groups show in Alert widget
We have devices that need to be members of multiple groups to keep our notifications simple. Currently, in the alert widget, all group memberships are shown in the Group column. We would like to be able to select which groups should be visible in the Group column. Usually it's the main business service group, and not the technical groups used only for alert rules. Also, we would like the groups in the Group column to be alphabetically sorted. Order seems random at the moment. Readability would be improved also if each group in the Group column was on a new line.10Views1like1Comment