MrTK

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

1 Neutral

About MrTK

  • Rank
    Member
  1. Problem When we onboard ESXi hosts we use esx.user/esx.pass, we do not configure SNMP on our hosts. We found that details about the host hardware and esx were not getting populated. Checked with support and they confirmed that LM uses SNMP to pull that information. Solution Wrote a PropertySource which uses the ESXi API (esx.user/esx.pass must be set), to pull the information. I used an existing LM DataSource as the basis for the script. E7T2C7
  2. This script makes the devices displayName the same as the sysName. It can be easily modified to update any property for any other property, or appending. We use a couple different variations of this script to keep our standard naming conventions consistent throughout LogicMonitor (and our CMDB). Made for API v1, I have not looked at how this might be different/easier with v2. Just sharing in case others find it useful. Script was adapted from a script example @Chengjie Zhu posted. import org.apache.http.client.methods.HttpGet import org.apache.http.client.methods.Htt
  3. This may not meet all your requirements, but another way to think about it. LM integrates with both SNOW and Slack, you could have your escalation chains simultaneously create a SNOW incident and post to the Slack channel for those Critical alerts.