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 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"Solved99Views8likes2CommentsIs 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?89Views1like4CommentsUIv4 - 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.78Views6likes10CommentsWhich 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!Solved68Views10likes1CommentRandom 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!Solved14Views1like4CommentsManaging Alert visibility on a "per-group" level
Good Morning all, we are a multi-Team managed service providerwho, surprisingly, manages customers team-wise. We are in the process of switching to LogicMonitor right now and we have some issues regarding shared devices and theirDataSource Instances, that belongs to different teams. We created Devicegroups for our teams, but if we put shared devices like loadbalancer, firewalls, storages etc. in said groups, ALL teams will see ALL alarms, regardless of responsibility. If one team decides to turn off an alarm on a shared device, the alarm is obviously deactivated on all other teams, as well. I'm aware of the Datasourceinstance grouping mechanism, but afaik it cant help with the problems i mentioned. We would like to request a feature where you can somehow mask datasources,their instances and their respective alarms based on the group you are in while you're viewing the device, so alarms andinstances that don't belong to your team doesn't show up at all. It would be really convenient to somehow configure a "view" of a device based on the group you are in that doesn't interfere with the devicedatasources. Bonuspoints if you bring in alarm-tuning in this somehow. :)/emoticons/smile@2x.png 2x" title=":)" width="20"> Regards, Bastian2Views1like3CommentsCustom 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.1View0likes1CommentGather 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 movethis 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 ofhaving 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 allinto groups.1View0likes3CommentsCollector 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.1View1like1CommentPermissions 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.0Views4likes1Comment