Recent Discussions
Monitoring for Mirth
Hello Community, We have a Mirth Appliance that we use for exchanging data with our partners. This is recently been added to our LogicMonitor instance but I'm only seeing what I would consider "basic" SNMP information. I can see data about the CPU, Disk, Memory usage. However, I don't see any "channel" information. This is something that's within Mirth and knowing if channels are clogging up, etc, would be handy to know. I don't know if this is something that can be reported on but according to this from PRTG https://kb.paessler.com/en/topic/80868-how-to-monitor-nextgen-mirth-connect-with-prtg It looks like it might be something that's reported through SNMP. I'm not an expert in SNMP/LogicMonitor so I'm coming to the community in hopes that one of you may already have something built that monitors Mirth Appliance channels. TIA!Kirby_Timm2 days agoNeophyte14Views0likes0CommentsBuilding Dynamic Groups using Powershell Batchscript DataSources
I'm looking for a way to use the "Description" field I'm collecting when building instances from a batchscripted datasource. current output I'm using in the active discovery writes WildAlias, WIldValue, Description: $($proc.processname)##$($svcmatch.displayname)##$toolname I want $toolname to drive instance grouping. I see mechanisms for using the other two, but altering those doesn't fit the use case I need for these. The Support Docs for instance grouping and for active discovery don't provide quite enough info to figure out what they're instructing without a bunch of experimentation (which is probably how I'll end up sorting this out if someone hasn't done this already). For instance (pun!), This refers to Dynamic groups ( dynamicGroup="^(.d.)" )... but does it only evaluate the GREP based on wildalias? Instance Groups | LogicMonitorSolvedCole_McDonald2 days agoProfessor32Views0likes1CommentAPI to put Multiple resource in SDT getting Authentication failed
Experts, I am trying to write a script to put multiple resources in SDT via API. However, the script fails with the error: "Authentication failed", "status":1401. This indicates that the API is rejecting my request. The API credentials are correct, as I am successfully using them for other API calls. Has anyone encountered a similar issue? Your insights would be highly appreciated.smahamulkar6 days agoNeophyte85Views1like8CommentsAlert/Alerts API endpoint
Hello Everyone, I am trying to get the list of all alerts through the API. Endpoint I am using is https://companyname.logicmonitor.com/santaba/rest/alert/alerts?v=3 Through this API I am only able to get the Uncleared Alerts. Now, Issue is I want all alerts including the one that has been cleared for reporting purpose. I would really appreciate if anyone could help me with this? Thank you, MnaishSolved103Views0likes4CommentsSQL Monitoring Troubles
Hey, I've just added 4 SQL Servers to our environment. 2 of them worked perfectly and are retrieving all the SQL data. However, 2 of them aren't learning that SQL is installed: one of them reports WMI access error but wbemtest from the LM collector with the LM collector account details succeeds on both. The other just doesn't seem to know SQL is installed, no errors are shown. The one with WMI error obviously isn't even retrieving Windows data like CPU and memory. The one with no WMI error is showing this data okay. I'm not sure where to check for problems in LM - any logs I can look at? Thanksldoodle25 days agoAdvisor54Views0likes4CommentsMonitoring of Veeam is not reliable
Has anyone successfully monitored Veeam with LM? From what I am seeing out of the box, every single module is unreliable. The scripts run probably 50-60% of the time. Otherwise they just fail with the error: Veeam Powershell snap-in was loaded from an incorrect location. This results in numerous "No data " responses. Which leads to issues with alerts not clearing when they should, or not opening when they should. Which cascades into our ticketing system to cause further confusion. Powershell works fine locally on any of the servers in question, scripts that utilize Veeam's powershell module that I push from our management tool also work fine. It just seems to be LogicMonitor that has issues with reliability. In these instances, the collector is installed directly on the Veeam host. Veeam forums indicate this may be due to the snap-in installation being corrupted, however I have manually verified it is all correct on a handful of servers and the issue persists. Plus it works locally and on my pushed scripts from a different tool. We are monitoring 44 Veeam servers (all the latest version) and all of them seem to have this reliability issue. Making it hard to believe that the installation could be goofed on every single one of them. All LM supplied default scripts utilize: Add-PSSnapin -Name VeeamPSSnapIn -WarningAction SilentlyContinue -ErrorAction SilentlyContinue I tested by manually running the script from a debug window, but changing from Add-PSSnapin to using Import-Module and referencing the Veeam dll file, yet the intermittent "incorrect location" error persists. Another test, I removed all references to Add-PSSnapin and suprisingly, it still works about 50% of the time. By all findings, I only get this error when running collection scripts from LogicMonitor. Have yet to see it locally. Anybody ese noticing the same thing?Solvedtk_baha2 months agoNeophyte156Views0likes1CommentLeast Privilege not showing full list of Windows Services
Using LogicMonitor in full admin mode (ie we connect with a service account with admin rights on the target windows server) has presented no issues. All metrics work perfectly, we can monitor ALL windows services. We are now rolling out "Least Privilege" to 1000+ servers and followed the step by step documentation and used the PowerShell script to apply permissions. The WMI aspects of monitoring work ok. However when monitoring "windows services" we can only see a subset of services. It seems anything that is out of the box before we install applications or solutions like IIS, SQL, Oracle etc etc does not appearing the list. Its noticeably a smaller list. Has anyone seen this in their environment? We are told there have been no other reports. If we make the service account a local admin - all services appear perfectly. In the documentation here: Windows Server Monitoring and Principle of Least Privilege | LogicMonitor there are 5 steps to eventually running a command "sc sdset scmanager...". This command also does not work. What are your experiences? have you seen the same issue and how did you overcome?135Views3likes10CommentsDuplicate interfaces being discovered while doing any IOS upgrade on devices.
Duplicate interfaces being discovered while doing any IOS upgrade on devices. Initially as per support we did some fine tuning on data source level, however recently this issue becomes more severe as we have lot of hardware changes planned. Anyone came across this issue or any solution for it? I know whenever any hardware changes happen there could be interface index value changes but we have 2-3 duplicate value of interfaces and we have to carefully disabled the one which does not have any data considering historical data.rana4153 months agoNeophyte89Views0likes1CommentLeast Privilege's script to set permissions on Services for Non Admin account.
With the new security push for us to use non admin accounts. If anyone would like I to have a script that can run on Domain and one for Workgroup Servers. That iterates though all services and applies correct SDDL for least privilege's account. Extract these to c:/temp, add your list of servers (or for the workgroup add the single server to the serverlist.txt) and then run the RunScript.ps1 You'll need a local admin account to run with for Workgroup Server You'll need a DA account to run for list of Domain Servers. PM me if you are interested ;)SolvedBarb4 months agoAdvisor201Views3likes5Comments