Recent Discussions
Instance discovery time
Hello, I was looking to is if anyone has created a module that would add the date and time a new instance is discovered for a module? I'm looking to determine when new interfaces are added to the network interfaces module on devices. I thought about changing the discovery script for that module to add the time but I cant determine where and how to add it so I tried creating a separate property source to do so but no luck. Any advice or insight is welcomed as well. // Assuming 'instance' refers to the current device instance within the PropertySource context def instance = context.device // Access the device object from the context, replace this with the actual method to access the device // Check if the 'discoveryTimestamp' property already exists def discoveryTimestamp = instance.getDynamicProperty("discoveryTimestamp") if (discoveryTimestamp == null) { // If the discovery timestamp doesn't exist, it's a new instance // Capture the current date and time in a readable format def currentDate = new Date() def formattedDate = currentDate.format("yyyy-MM-dd HH:mm:ss") // Add the discovery timestamp to the instance's dynamic properties instance.addDynamicProperty("discoveryTimestamp", formattedDate) // Output the discovery timestamp (This is logged in the script output) println "New instance discovered at: $formattedDate" } else { // If the property exists, it's not a new instance println "Instance already discovered. Timestamp: $discoveryTimestamp" }
LM Tokens can they be broken down
Hi, We have a ServiceNow integration and use the ##EXTERNALTICKETID## in our alerts views and dashboards. However I believe tokens are clunky and not particularly granular. For example ##EXTERNALTICKETID## also contains the integration name as part of the token. Something we do not want all we need is the TicketId as per the JSON payload. In addition it is not possible to rename the column header is alerts and dashboards. This makes look untidy. Would it be possible to have something like: ##EXTERNALTICKETID.TICKET## with the ability to have a DISPLAYNAME option ##EXTERNALTICKETID.INTEGRATION##with the ability to have a DISPLAYNAME optionDoes anyone have a Module just to check if SNMP is working at all?
Hi, We have a lot of times where a server will stop responding to SNMP checks for whatever reason. That will generally turn CPU, File System, Uptime, etc all to No Data responses. We generally have No Datas set to Not generate alerts so we don't get spammed with things. However, if snmp really does stop working, we'd want to know that so we can go fix whatever the problem is. We currently have Host Uptime set to generate an alert on No Data, but it usually gets ignored because people think it's because something got rebooted recently or something. So, I want to setup a check that just does the most basic snmp check it can, something that every device should respond to, and can then alert if it doesn't get a response. I looked in the Repository and didn't see anything official from LM for this, but did see a community created Module that might work. It's called SNMP_Troubleshooter and there are two of them for some reason. The older one has a newer version # which is a bit odd. Anyway, all it does i: import com.santaba.agent.groovyapi.snmp.Snmp; def host = hostProps.get('system.hostname'); try{ oid_value = Snmp.get(host, ".1.3.6.1.2.1.1.2.0"); println "snmpStatus=0"; } catch (e){ println "snmpStatus=1" } return 0 Does anyone else this, or something similar, to find machine where snmp is dead? I see this person also has an WMI version as well which would be great for when WMI dies as well. Thanks.
Halo PSA - Integration
Hi, we are currently moving away from AutoTask into HaloPSA. We've been given the instructions from the vendor however, if we follow these instructions the ticket information won't be passed back to LM and auto closing of alerts could potentially fail. Has anyone had success using JSON to integrate or do we need to fall back to XML despite instructions from Halo.
LogUsage data source
Hello, We are having all our devices sending syslog to LM collector. Via LogUsage data source, we can monitor if the device sends syslog data or no. But the threshold to alarm on that is only 60 minutes. We would like to make the threshold longer like 1 or 2 days because some devices are quieter than others, and we want to control if we missed to configure syslog on one of the devices or it doesn't send syslog anymore due to any reason. So, i contacted LM support, they said it would be custom datasource. Any help with how to achieve that?
