David Lee

LogicMonitor Staff
  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About David Lee

  • Rank
    Community Whiz Kid
  1. Hi Ben, https://www.logicmonitor.com/support/settings/collectors/using-the-collector-debug-facility/ Uing the collectors debug facility detailled in this help page can show you which devices are failing to respond to wmi. The command to use would be !tlist c=wmi This will show a long list of all wmi tasks on all 56 devices, search through for any that do not say OK, (a good tip here is to use control-F and search for "WMI query task failed")and the relevant device name will be shown along with an error message, If you need further help just hop onto chat where I or a colleague would be glad to help you, I had a look at your collector and can see several hosts failing wmi but I obviously wont paste them in here as this is a public forum. David
  2. Hi Mac, LMsupport would love to assist you with this issue, but we are not certian which portal is yours. FYI, you should really raise a chat request these forums are not monitored routinely by support engineers. David
  3. Hi Josh, It's been a while since your request, sorry I didnt spot this a couple of months ago. We have propertysources now, a simple groovy script will do this for you. def hostname = hostProps.get("system.hostname") def OID_contact = "" // the OID we want def contact = Snmp.get(hostname, OID_contact); println "contact=" + contact def OID_system_name = "" // the OID we want def system_name = Snmp.get(hostname, OID_system_name); split_name=system_name.tokenize( '.' ) println "system_name=" + split_name[0] def OID_location = "" // the OID we want def location = Snmp.get(hostname, OID_location); println "location=" + location return 0 If you need any further pointers hop onto chat, David
  4. Helping us to help you Our job here at Logicmonitor technical support is to help you in your day-to-day work. Whether your report isn’t emailing out, a device is not responding to WMI or you don’t understand why a particular alert is occurring – we’re here to help. But when you submit a ticket it is usually in a queue, being British I love queues! But the support team hate making people wait so anything we can do to make the queue smaller means you must wait less for a response. So here are some tips to help us help you faster. Write a Descriptive Summary Use wording in the subject of your email or the summary of the web form that states what the specific problem is and what you are seeing. Try using something like this: Alert LMD12345 on device myhost for SQL does not appear to be correct Instead of this: False Alert??? When our team sees the first ticket we can immediately route it to one of our team members who has more experience with SQL. The second line requires us to open the ticket and read the details. Details, Details, Details! In the body of the email (or the details section of the web form) put all the relevant details to the problem that you can think of. Anything you may know that is relevant will help our team get to this faster. Try to include · The device name or service name · The alert ID of relevant alerts · The datasource name · The full URL of the page where an issue can be seen such as the device URL, or a datasource URL. · Any debug commands you have tried, if any · If the issue happens on a regular time basis when is that? · If it’s a UI issue what browser have you tried? · When did you first notice this? · What datasources do you believe should be on a particular host? Include everything you can and help us resolve your issue in a timely manner. Follow Up “My ticket has been open for three days and no solution provided as yet.” We do our best to answer tickets as they come in. Sometimes we are faster than others. Often we need to co-ordinate with our development team to fix an issue. A good way to update your ticket is to reply to the ticket email. Creating a new ticket asking about an old ticket means we have to find the older ticket, find out who that was assigned to, merge the tickets and notify whoever was dealing with your ticket. Replying straight to the original ticket goes straight to the person who was dealing with your request and can be a lot faster.
  5. We sometimes see datasource scripts with passwords in the body of their script. For testing this is fine, but in production datasource scripts, passwords in plain view isn’t just bad, it should be a cardinal sin. You can use Powershell to secure a password by creating a PSCredential object that uses the cmdlet Get-Credential and stores the output into a file. Note that it saves as a System.Security.SecureString. Now you can use the file in your script: $hostname= "##HOSTNAME##" $pass= Get-Content "\\Encryptedfile.txt" $user= "##PS.USER##" $password1= ConvertTo-SecureString -String $pass When your script is finished just run it in powershell GUI to check it works fine. Make sure you alter our tokens to the correct values. We had a recent case that when the collector tries to run the datasource script it failed. The below error was in the logs. New-PSSession : [PROD-TP-DB01] Connecting to remote server HOST failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. The script is failing with an authentication error. Even though it works fine in the Powershell GUI. The reason for this was the account the collector ran under. PowerShell uses the Windows Data Protection API (DPAPI) to encrypt/decrypt your strings. That means if you created the file using one user account only the same user account on the same computer will be able to use this encrypted string. So the collector account cannot read the file Encryptedfile.txt. We proved this by running the Powershell GUI under the same account your collector uses. So make sure that you create the file using the same account. Keep in mind that if you change the collector account, the script will fail. It is possible that you can encrypt the file using a machine key, which means any user on the collector can use the file and decrypt it, but that’s for another post!
  6. Thank Jeroen, Most kind of you. David
  7. The graph that Raz is referring to is a dashboard graph which has different datasources from different hosts.
  8. Hi Ben, Data is still in the midst of being transferred, so not everything is here just yet. The old support forums are still there with comments, such as yours https://logicmonitor.zendesk.com/entries/62044854-please-clear-alert-acknowledge-when-severity-changes But eventually everything will be moved to https://support.logicmonitor.com/customer/portal/topics/766861-feature-requests/articles If you can please bear with us for a little time this should be rectified, if you know what threads in particular they were I can keep an eye on them, David
  9. HI,rn rnThe access log goes back 60 days and you can already download it by pressing the download button at the top right. This gives you a CSV file of the log,rnDavid