All Activity

This stream auto-updates     

  1. Yesterday
  2. Collectors for non-routable vlans

    anyone ? I would imagine a lot of companies have this challenge
  3. @Dave Lee Q, Do you have a sample script on how to return the last value? Is there some built-in api to get the prev value? should I store it in a file and just use that value?
  4. Last week
  5. Bandwidth report on an interface

    I agree, it would be good if LM could do this
  6. What do you suggest setting up the collectors for monitoring non-routable vlans or no-internet vlans ? I don't want to use the Proxy option , because that would involve changing the layer 3 network. I am thinking about building dual NIC collectors, and use 1 nic for collecting, 1 nic for Internet traffic. My questions are: Does LogicMonitor recommend this method ? Do you have any thought ?
  7. Infoblox Monitoring

    Could you please add Infoblox as a recognized datasource? https://docs.infoblox.com/display/MAG8/Infoblox+MIBs We would like to monitor our DNS/DHCP infrastructure
  8. Custom Alerts for ConfigSources

    Seconded! ConfigSources could be a really powerful tool, but the only reason I'm not using it much is because I can't customize the alert notification content. Context is everything in monitoring.
  9. Dynamic Tables

    I found this because I just tried for the first time to add a table and was floored that I must define every row by hand. In this case, I have to work around the lack of "bottom N" in graphs so I can watch for devices that have rebooted recently in one place. I want to put in this table all devices in a group, which seems like a no-brainer from a functionality standpoint. Having to manually define those and maintain forever is a non-starter. Can we please get the rows to be enterable as device groups and/or globs, as in other places? Thanks, Mark
  10. VMware "In­-Guest" DataSources - Version 1.0 - LogicMonitor Custom Development Summary: The following provides information and deployment instructions for the application of hypervisor-­level monitoring data - as presented within a Windows virtual machine in LogicMonitor. There are three "In­Guest" VMware DataSources ­- they are: VMware_vSphere_VMperformance_InGuest (locator code: CHLF7C ) VMware_vSphere_VMsnapshots_InGuest (locator code: 9YF42D ) VMware_vSphere_VMstatus_InGuest (locator code: ZMEJ6P ) How it Works: These datasources were cloned from the official LogicMonitor VMware DataSources ­ with ‘_InGuest’ appended to the end of the standard name. They have been altered in the following fashion to apply them 'within' the virtual machine device: A critical feature built into the DataSources is the ability to ‘override’ a vCenter location with ‘esx.url.’ ○ This allows us to apply the DataSource to a VM and point it to vCenter for data. The AppliesTo language is updated to apply the DataSources to Windows Virtual Machines: ○ system.model =~ "Vmware Virtual Platform" && esx.url && esx.user && esx.pass The host property variable is switched from system.hostname to system.sysname: ○ def host = hostProps.get("system.sysname") The Active Discovery of virtual machines is limited to the device hostname to which it is applied: ○ ManagedEntity[] vms = new InventoryNavigator(rootFolder).searchManagedEntity("VirtualMachine","${host}"); Implementation: Three properties are required to be applied to the virtual machine device(s) in LogicMonitor: esx.user esx.pass esx.url in format: https://<vcenter­ip­address>/sdk Once the device properties are present, the AppliesTo language will kick in and the DataSources will apply. Suggestion: create a dynamic group of Windows virtual machines, and set the ‘ESX’ properties at that group level. Notes: ­These DataSources are custom development and officially unsupported by LogicMonitor. Restrict the application of property esx.url to ONLY the virtual machines needed. This property will apply to ESXi hosts if allowed, which impacts vCenter collection and performance. Deploy this in stages - we will be increasing the load on vCenter due to the additional API queries. We do not currently identify Linux VM’s out of the box, for now this is Windows-­only. Automated detection of VM to vCenter relationship is difficult at the device level, hence the need for esx.url. vCenter is the preferred integration point for esx.url, but an ESXi host should also work (until the VM moves.)
  11. Office 365 Monitoring in LM Cloud

    Hey Matt - Note that we support monitoring of Office365 email availability & performance using our Email Service Monitoring datasources. Have a look at: https://www.logicmonitor.com/support/monitoring/applications-databases/email-service-monitoring/ for details. A number of other Office365 services can be monitored with custom service checks. More info at: https://www.logicmonitor.com/support/services/adding-managing-services/adding-a-web-service/ -m
  12. Office 365 Monitoring in LM Cloud

    Hi Matt, Thanks for posting. We're looking into adding support for Office365, and will post back once we have more details. Thanks! Sarah
  13. Office 365 Monitoring in LM Cloud

    Can Office365 monitoring be added to LM Cloud?
  14. Alerting on difference to historic value

    you "could" do this with a complex datapoint using groovy (https://www.logicmonitor.com/support/datasources/creating-managing-datasources/creating-complex-datapoints-with-groovy/) and using the get data rest API to retrieve the value you're looking for and do the math. It's complicated to do, but feasible. This would be a good idea to raise in the feature requests, I believe others have asked for this same functionality.
  15. Time Zone setting at the User level

    @MoshI wish it was only large global enterprise customers. We are setup as an MSP and shockingly have clients in different timezones than ours. It is only a bit embarrassing to explain to those not in US/Pacific why they cannot see their graphs and other data in their local time.
  16. Time Zone setting at the User level

    Hi @Annie Dunham, I'm not convinced LogicMonitor understands just how big of a pain point this is for large global enterprise customers.
  17. Time Zone setting at the User level

    To make matters worse, today I noticed that Windows event log event timestamps are sometimes out by an hour from GMT. "This is actually being worked on now. Design is done, and its going to Dev in the next sprint - so barring issues should be available in the near term." @Steve Francis That was in 2015, surely there is some progress?
  18. @Sarah Terry @Steve E Yep, it was URL encoding for me in the case of PHP. Weirdly though ASP.NET wasn't working but it now even though I haven't modified the code to URL encode.
  19. Exchange Online and Hybrid Exchange monitoring?

    Thanks Kerry - that's great. Our company is rolling out O365 and Azure increasingly - if this could be added to the Cloud Monitoring platform, I think it would make a great addition. I'll play around with those Powershell examples you provided as well.
  20. Used to detect for event id's of 4776 and 4625 in the security logs XDYCH4
  21. Failed RDP Attempts

    Nevermind... I have done it myself for anyone who wants it... I will be adding this to the exchange forums. XDYCH4
  22. Custom Alerts for ConfigSources

    Hey LM team, There are a number of options to customize what is in a service alert as well as a data source alert, but config source? Nope, can't modify what gets sent. All it says is that a change was made and gives you a link to the device. A couple things I think would be beneficial as a new feature, 1. Being able to put what lines were added or removed right in the alert. For simple configs you can then tell right away if you need to take action or not. 2. Have the link in the alert actually bring you to the diff view of the current and last config state. While having to click through the multiple links and then slide the diff view slider is fairly painless, at 3am on my phone it can add to the sleepy frustration level. Basically just bringing some of the flexibility that alert templates have for data sources and services to the config sources. Thanks!
  23. Failed RDP Attempts

    It would be nice if we had a way to track failed RDP attempts. This would be super useful to detect brute force attempts. I know this can probably be done with an event source.
  24. RDP Sessions

    This is good... actually it's really good. Thank you
  25. @Sarah Terry Just tested your script. It worked, however it seems the difference is how the two programming languages (Mine being Salesforces Apex) encodes the URL. Python seems to automatically encode the URL, on send the '>' is converted to '%3E' which makes sense. Apex does not automatically do this. When I replaced the '>' with '%3E' in my code, it worked. That might be the issue @Mosh is having as well. Might be worth noting the encoded URL characters in the filter sections of the knowledge articles... Thank you for your help!
  26. @Mosh @Steve E Here's the request I'm making, which is successful (I've included the full python script): #!/bin/env python import requests import json import hashlib import base64 import time import hmac #Account Info AccessId ='ACCESS_ID' AccessKey ='ACCESS_KEY' Company = 'COMPANY_NAME' #Request Info httpVerb ='GET' resourcePath = '/device/devices' queryParams = '?filter=updatedOn>1477952627' data='' #Construct URL url = 'https://'+ Company +'.logicmonitor.com/santaba/rest' + resourcePath + queryParams #Get current time in milliseconds epoch = str(int(time.time() * 1000)) #Concatenate Request details requestVars = httpVerb + epoch + data + resourcePath #Construct signature signature = base64.b64encode(hmac.new(AccessKey,msg=requestVars,digestmod=hashlib.sha256).hexdigest()) #Construct headers auth = 'LMv1 ' + AccessId + ':' + signature + ':' + epoch headers = {'Content-Type':'application/json','Authorization':auth} #Make request response = requests.get(url, data=data, headers=headers) #Print status and body of response print 'Response Status:',response.status_code print 'Response Body:',response.content
  27. RDP Sessions

    Security reviewed. Great job
  1. Load more activity