Recent Discussions
Availability Group- multi-subnet Listener
Received two critical alerts in Logic Monitor for Host Status and Ping for Availability Group's Listener. The AG is healthy - looks like there is a configuration issue in LM that if a failover occurs on an AG with a multi-subnet listener the alert check fails. Shouldn't the check be on the listener name which can resolve to either IP, not a single IP address? I had different IP when added Listener (Manage-IP address) and different IP in jdbc in properties because it's multi subnet listener. I just changed the IP in settings (Manage-IP name) and jdbc connection string so it matches the Listener IP but he next time there is a failover it'll start alerting again. How do I change the properties for Listener so whenever there's failover it can resolve to either IP address? Would it be just as simple as setting up Listener's DNS name in section of Manage tab and adding listener's dns in jdbc in properties?lucjad8 hours agoNeophyte
16Views0likes4CommentsLogic Monitor Collector Installation- Prompt for proxy address and port
I was trying to install Collector on the customer server and received message asking for proxy address and port. I don't have networking expertise so it's kind of confusing. How do I get this information? Collector is installed but not communicating with Logic Monitor so I can't edit proxy settings there. Also, the server has a carbon black error but it was disabled during the collector installation. How would I whitelist the proxy address to Logic Monitor datacenter so carbon black error wouldn't interrupt with anything. Where do I get the proxy address?lucjad8 hours agoNeophyte
53Views1like5CommentsNetwork Interface ID Persistence or: How I Learned to Stop Worrying and Love SNMP_Network_Interfaces
RE issues like these: How is everyone else handling network interface ID changes? | LogicMonitor - 14445 Network Interface - Duplicates/Nulls | LogicMonitor - 15666 This is a very common customer issue when the device either does not support, or is not enabled with, "snmp ifindex persist". This can cause duplicate DataSource instances being created when these IDs are updated. The ultimate fix here is to enable snmp ifindex persist, but that might not be an option. For just a bit of context, the ifIndex is the only thing that is guaranteed to be unique across all vendors which is why it is the WILDALIAS (unique identifier). All this to say, there is no one-size-fits-all solution. Our module team made this choice to lower the potential risk of losing data and to provide the most reliable core/supported solution. I'm creating this post in hopes of providing people with options and help lower the number of support tickets we see about this 😁. This post assumes the reader understands the basics of Active Discovery and the difference between wildalias and wildvalue. This is a great learning resource: Introduction to DataSources 🚨Now entering unsupported territory! 🚨 Since I am in Support, I am obligated to mention that the following solutions arenot supported by the LM Support team. Customers should exercise caution and thoroughly test any and all workarounds within their sandbox portal. We highly highly recommend cloning the core "SNMP_Network_Interfaces" DS first! You will very likely lose historical data. I'm also only going over this using "SNMP_Network_Interfaces" and not the DS for Windows or SSH interfaces. You have been warned. Alright already... so what's the fix? Well, there are 2 main workarounds. Option 1: WILDVALUE as ifName and unique identifier Portal version 204 had an update for the DataSource "SNMP_Network_Interfaces" to allow using ifName instead of ifIndex for the instance WILDVALUE with the host property "interface.wildvalue.ifname". Release note mention: https://www.logicmonitor.com/release-notes/v-204-release-notes#h-updated-logicmodules Mention in SMNP Network Interface Monitoring support page: Mention in "SNMP_Network_Interfaces" technical notes: So that's all cool, BUT (and this is crucial) the unique identifier for instances is still the WILDALIAS which remains unchanged by this whole thing... You will then need to toggle on "Use Wildvalue as Unique Identifier" within the DS settings: *** This isNOT reversible and will result in loss of historical data. Also, enabling this on a core module will impact your ability to import updates to that module. *** Ok, sorry just really have to make sure that's super clear... After that, you should be all set. If the ifIndex updates, the WILDALIAS will update with the new ID but the WILDVALUE will remain the same (unless for some reason the ifName also changes) and no new instance discovered. YAY! 🎉 Option 2: Change the Active Discovery script This is certainly the more flexible workaround. I mean you can update the Active Discovery script to do literally anything. The simplest change is to just remove the ID from the WILDALIAS. Again, be sure to CLONE the DataSource first! That would look something like this. This line (around line 320): def alias = "${ifEntry.description} [ID:${ifIndex}]" would be updated to be: def alias = "${ifEntry.description}" of course there are other potential tweaks but this is all very much dependent on the environment and each device. For example, with this specific edit, the uniqueness is now dependent on the interface description which, as previously mentioned, might not be unique. You can set this 'alias' variable to the ifName or something totally different if you really want. But, again, you should be all set. YAY! 🎉 In both scenarios, I would recommend only applying this cloned version of the SNMP_Network_Interfaces to devices that don't have the option to persist the ifindex and keep the core version applied to all other devices. Feel free to share any other workarounds you may know of or are using!mray9 hours agoLM Conqueror
52Views5likes1CommentAPI documentation error
The page linked below refers to an alert type called websiteAlert. websiteAlert isn't what LogicMonitor sends when a website reports an issue; we get serviceAlert instead, which isn't mentioned. As we often build logic based on alert type in AlertMagic, having the wrong type listed is a problem for us. It's also not clear what type of alert will be sent when a service alerts. www.logicmonitor.com/support/logicmodules/about-logicmodules/tokens-available-in-datasource-alert-messages Whatever the fix, please don't make it a breaking change!David_Bond9 hours agoExpert
11Views0likes1CommentSNMP Monitoring for Windows
We have a customer with a highly locked-down Windows environment. They would like to get the most they can from SNMP monitoring of Windows. Does anyone have any tips on enhancing the basic SNMP information as provided by Windows, either with any changes to the monitored Windows environment OR additional DataSources etc? Many thanks in advance!David_Bond9 hours agoExpert
15Views1like1CommentSQL Server connections using mssql.<instance name>.mssql_url
For some SQL Servers due to how they are setup, we are setting the property mssql.<instance name>.mssql_url I've noticed, when I do this, the Microsoft_SQLServer_Connections module then does not retrieve the SQL Server version and edition (e.g. Enterprise, Standard, Express), which is affecting some custom dashboards. What's the best guidance to resolve this, would I need to create my own datasource?Damian12 days agoNeophyte
23Views1like3CommentsSQL System Jobs- ability to detect if an Integrity Check has not been run on databases
Is there a way to get notified about SQL System Jobs in Logic Monitor- specific job that was not run on databases? I have some servers that need ability to detect if an Integrity Check has not been run on databases. Meaning Logic Monitor's ability to detect specific SQL Server was missing the Integrity Check job. (Without adding that job under the SQL System Jobs).lucjad3 days agoNeophyte
24Views0likes1CommentResource Explorer
Hi, When utilizing the newly released "Resource Explorer" I am attempting to Group by: "Resource Type" these grouping has a lot of "No Resource Type" and "Unknown" resources being grouped together, when I drill into them I clearly know what type of resources what they are, some switches, routers, net storage and other such things. Does anyone know a way to "Tag" the resources in the "Resource Explorer" to clean this up? If, you have a better training then something provided on LM Academy or you can find via of a Google search that would be much appreciated.JosiahBenoit3 days agoNeophyte
62Views0likes9CommentsPermissions lost in Module Toolbox
In the Module Toolbox, it looks like users now need "Manage" permission to Logicmodules in order to test Active Discovery against a device and use certain other features. This is because you now have to click "Edit" on the module to access the Active Discovery test button. When we had access to Logicmodules on the Settings page, users were able to test Active Discovery with View-only permissions to Logicmodules. So now our NOC no longer has permission to test Active Discovery and is impacting their ability to troubleshoot certain issues. It really does not make sense that we have to open the "Editor" for the module in order to access features like testing the discovery/collection scripts, seeing "Show associated resources", or exporting the file of the module. None of these things are related to editing the module, yet you now need "Manage" permissions to use them.Matt_Whitney3 days agoAdvisor
26Views1like1CommentCollector Bouncing
I have a collector where the service is stopping, I checked the logicmonitor-agent-control.log file and I am seeing something about an illegal reflective access, could this be the cause of the service stopping? I'm not seeing anything in Event Viewer that helps. The error from the log is below. Let me know if more information is needed. LOG: [24-07-23 12:47:22 PDT][Thread-Thread-4][WindowsJavaProcess.access$000:31]: APP-ERR: WARNING: An illegal reflective access operation has occurred [24-07-23 12:47:22 PDT][Thread-Thread-4][WindowsJavaProcess.access$000:31]: APP-ERR: WARNING: Illegal reflective access by org.rzo.yajsw.app.WrapperJVMMain (file:/C:/Program%20Files/LogicMonitor/Agent/lib/wrapperApp.jar) to field sun.management.RuntimeImpl.jvm [24-07-23 12:47:22 PDT][Thread-Thread-4][WindowsJavaProcess.access$000:31]: APP-ERR: WARNING: Please consider reporting this to the maintainers of org.rzo.yajsw.app.WrapperJVMMain [24-07-23 12:47:22 PDT][Thread-Thread-4][WindowsJavaProcess.access$000:31]: APP-ERR: WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations [24-07-23 12:47:22 PDT][Thread-Thread-4][WindowsJavaProcess.access$000:31]: APP-ERR: WARNING: All illegal access operations will be denied in a future releasejoshlowit13 days agoNeophyte
30Views1like3Comments