Recent Discussions
Collector configuration management - API/Ansible
Hi, We recently had to change the collector cache to a new baseline. Needed to be applied to every collectors. To avoid slow and repetitive actions, we tried using APIs/Ansible. But to my understanding the following APIs call don't support "Agent config" changes : /setting/collector/groups/{id} /setting/collector/collectors/{id} Also tried using Ansible lm_collector module https://galaxy.ansible.com/ui/repo/published/logicmonitor/integration/content/module/lm_collector/Virgil_Soulie20 hours agoNeophyte32Views0likes2CommentsAlert Exports : Please add export to CSV option
From the Alerts Option, I can build my custom alert (filtered on Datasource, group etc). Select the time period. Then.... I need to take a screenshot to send it to someone. Or start the work again with an Alert Report. Can we get an export to csv/pdf option?ryang2 days agoNeophyte19Views1like1CommentActive Discover Filters with non-existent properties
I've been looking for an easy way to exclude instances by manually creating properties like ##exclude.volumes## or ##exclude.replicationjobs## which can be referenced in Active Discovery filters. Normally you can use something like NotContain or RegexNotMatch (ie "Name NotContain ##exclude.volumes##") but that only works if the property exists. If it doesn't existing (which provides an empty string) then that filter ends up excluding everything. Which means you can't just add it when you need to exclude something. I tried several different ways to write regex to make this work but I don't think it's possible (but open to hearing a way!). Note that this needs to account for instances that can change automatically, like temporary drive mounts for example. So just disabling the instances manually wouldn't be enough. I also don't really want to set a "default" value for all these possible Exclude properties at the root level. I also wanted something that can be easily modified on any existing multi-instance DataSources, including common built-in ones and DataSources that just use WMI or SNMP without scripting. I could clone the existing DataSource and switch to using a scripted Active Discovery to deal with it in code. But I already have so many parallel DataSources with official ones and a simple Filter change would be better. So what I would like to see, and I'm sure it's come up before, is for Active Discover filters to support nested AND. So a filter can contain something like (##exclude.volumes## Exists AND Name RegexNotMatch ##exclude.volumes##). That should provide a way to do what I'm looking to do. Or something that might be easier but messier is a new option like NotContainUnlessBlank or similar that will ignore values that are blank, although that sounds messy and confusing. I'm open to any suggestions to workaround if anyone has any.Mike_Moniz2 days agoProfessor2Views0likes0CommentsService nesting and topology mapping
I would like to see that services can be be nested and relationship based on the nesting with alert settings on the relationship. For instance we have products that contain multiple components now each is monitored and using group strucure we can kind of do a root cause. But it we can use services with maps and build relationships between them we could for instance see that a website goes down because on a sql server the logdisk fails. the service than from a user perpective is the website. But from tech perspective it is the whole chain. If we can use services to include the websitecheck, the webserver, the database, the hardware stack each connected using a service depending on the other service shown on a map would directly point you to the root cause. Guess here LM lacks in my opinion.13Views0likes0CommentsAlert Tuning : Please add export to CSV option
This comes up on a weekly basis for us but can you please add the ability to export all the items displayed on the Alert Tuning tab to a CSV. Many clients, dev groups ask us for a report on all the metrics that we are monitoring for a group of devices, location, technology and what thresholds are in place. The alert tuning tab has exactly this info but we cannot share with anyone in a meaningful manner. The "Threshold Report" is not a viable option as it spits out EVERYTHING and quickly maxes out on the 50k line limit. We just need the Entries listed in the Alert Tuning tab when clicking on a any device in the tree.DanB8 days agoAdvisor177Views6likes6CommentsUIv4 Dashboards Page - Table Widgets and instance-level properties
In the new UIv4 dashboards page, we are now able to add properties to a Table Widget as columns. However we can currently only add device-level properties to Table Widgets. It would be really useful for a lot of use cases if we could add instance-level properties to a dashboard widget as well. For example if we had a table which showed interfaces, it would be useful to be able to show instance-level properties of the interface such as the interface description or interface vlan. Also being able to use the ##DSIDESCRIPTION## token within a table widget would be useful for the instance description, but we cannot do that either.Matt_Whitney10 days agoExpert192Views9likes10CommentsRequest for OpenGear device monitoring
We recently had to add several Opengear devices to meet a use-case demand that was given to us. It would be helpful to be able to monitor them with Logicmonitor. We are using the Lighthouse management application in conjunction with models of OM1200 and IM7200. It might not be necessary to monitor each device since it looks like Lighthouse can act like a vCenter (telling you all about individual nodes and guests without having to directly monitor each ESXi node): "Lighthouse can be configured to expose managed node information such as node name, node model number, node port label, license status, etc. via SNMP" orgLighthouseMib interesting OIDs include orgLhNodesConnected orgLhNodesDisconnectd orgLhNodesPending orgLhNodeUptime orgLhNodeConnStatus orgLhNodeCellularHealth Then, as phase 2, it would be valuable to monitor each device directly to get common things like CPU, memory, interface, power supply status. Please +1 to get this into the dev pipeline. thanks.Solved132Views1like1CommentFeature request: SDT timings similar to Patch Tuesday schedules in Azure
Basically within azure you can schedule patches for the second Tuesday of the month +n days so you can apply patches the Thursday after patch Tuesday, which doesn’t necessarily fall on the second Thursday of the month, Take the current month as an example, the second Thursday falls before patch Tuesday Would love a feature option with SDT to accomplish this for more automation instead of having to set up an SDT for patching every month.NHale10117 days agoNeophyte145Views3likes2Comments