pperreault

Members
  • Content Count

    14
  • Joined

  • Last visited

  • Days Won

    3

Community Reputation

3 Neutral

About pperreault

  • Rank
    Community Whiz Kid

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. pperreault

    Public IP Property Source

    Thanks for this, this is great. I am only interested in the ip and org info so in the interest of de-cluttering the property source info I reduced the script output to just that. Stack Exchange (since I'm not a groovy guy) pointed me to this solution. //comment out orig map iteration //arrayInfo_map.each{ key, value -> println "$key=$value"}; def ip_addr = arrayInfo_map.find{ it.key == "ip" }?.value; if(ip_addr) println "ip = ${ip_addr}"; def carrier = arrayInfo_map.find{ it.key == "org" }?.value; if(carrier) println "org = ${carrier}"; I wouldn't be surprised if improvement on this is possible. Thanks again.
  2. pperreault

    collector fail count

    One of our collectors is experiencing what seems to be connectivity issues. Common symptoms are it loses communication with the LM cloud, remote sessions to it or monitored devices fail to complete. I also notice that the collector heartbeat fail datapoint is increasing with time. I've seen it's value over 6000. Support hasn't been able to tell me what this value actual is other than providing developer notes, which are unfortunately unhelpful. Can anyone provide some insight to what this failure count is actually counting? Has anyone seen and resolved this symptom? We are planning on rebuilding the host server and recreating the collector.
  3. pperreault

    Alert Supression Logs

    It would be beneficial to have direct access to logs indicating when alerts are suppressed due to escalation chain rate limits. Currently these logs are only available through support.
  4. pperreault

    Running vs Startup Comparison ConfigSource (PoC)

    I tried pulling this configsource but it looks like it is under security review. Any idea when it will be available?
  5. pperreault

    DataSources_List PropertySource

    It seems YH9ZXM is unavailable due to security review. Is there a stats on this?
  6. pperreault

    Meraki Multiple Organizations

    So far so good, no issues with this hack for monitoring Meraki networks as of yet.
  7. pperreault

    Meraki Multiple Organizations

    We manage multiple Meraki organizations and have been limited by the one collector per organization rule. Monitoring a Meraki organization via the Meraki cloud requires snmp.meraki.com be used as the IP Address/DNS name with the organizations unique snmp settings. A collector requires unique IPaddress/DNS name for each Logicmonitor device which prevents multiple organizations from being monitored by the same collector. To circumvent the one controller per organization limitation we've created internal DNS c-name records which point to snmp.meraki.com and use those as the IP Address/DNS name entry for different client organizations. We are currently running this as a test and haven't experienced any issues to date. I'd like to know if anyone else has experience with this (or any other) workaround, if so if any issues were experienced or if anyone can identify potential problems. Thanks
  8. pperreault

    Dependencies or Parent/Child Relationships

    Has using an empty value for the depends_on property been tested to have negative results? My testing shows no ill effect. Adding this property at the group level obviously speeds deployment. However if the primary device is within the group I don't want to make it dependent on itself. Adding the depends_on property to the primary device with an empty value seems to resolve this.
  9. pperreault

    Cisco ASR configsource

    Cisco_IOS excludes the ASR platform. Is there a plan to create a unique configsource for the ASRs or update Cisco_IOS?
  10. We are an MSP migrating an existing client base to LM for network and voice infrastructure health monitoring. For ease of deployment, when we do not manage their server infrastructure, we are thinking of providing clients with an ova to deploy within their network. Once the VM is deployed the collector will be installed. Any words of wisdom or lessons learned from your experiences doing something similar would be appreciated.
  11. pperreault

    Delete instance groups

    My mistake, this does exist.
  12. pperreault

    custom speed for interfaces

    This is fairly standard functionality in a monitoring tool. Many WAN circuits will be delivered at a rate limited speed. As an example, a carrier circuit may be clocked at 100Mbps or 1Gbps while the service speed is limited to 10Mbps, 20Mbps or 50Mbps. Utilization reporting, alerting and forecasting should be tied to this service speed, not the interface clock rate.
  13. pperreault

    Delete instance groups

    Feature request to delete instance groups. device > data source > instance > instance group because sometimes we want to undue what we've done
  14. pperreault

    custom speed for interfaces

    Is there an update on this feature request? To reiterate the request, it is important to be able to specify a service speed which can be different than a physical interface speed. The physical interface speed being what is learned from the SNMP poll. Then of course, we need to be able to graph, trigger alerts, etc based on this service speed. If you want to be complete, you'll include both an In service speed and an Out service speed as these are sometimes different.