Recent Discussions
Using !snmpdiagnose
I've been having a play with the !snmpdiagnose command in collector debug. I assume I should be providing the OID I want to query at the end of the command, like you would with the !snmpwalk command. It seems to ignore whatever OID I put at the end though, and always tries to query .1.3.6.1.2.1.4.20.1.1. I've tried it with and without the leading dot. If I use !snmpwalk with the same OID, I get the results I'm expecting, so I know the OID is on the device. What am I doing wrong here?69Views0likes9CommentsBest way to deal with "dynamic" SNMP data
I think this may be a bit of a unique scenario but I also think there might be a better way to deal with this than what I've tried so far. We're setting up LM to monitor a Crestron control system using their SNMP interface. Crestron supports some of the standard SNMP MIBs for reporting health of the control processors (e.g. Host Resources etc.) and then has a separate "IO" MIB that allows for reporting the status of various devices/systems that the control processors interface with. The main part of that MIB that I'm working with is essentially a table of status parameters (DataPoints in LM lingo), with each entry having some info about the parameter like the name of the parameter and the associated device, the current status, high/low value descriptions, etc. Couple simplified examples for purposes of this discussion: Table Entry 1 "Audio System" <-- Device name "Online Status" <--Parameter name 1 <-- current status "Online" <-- "1" description "Offline" <-- "0" description Table Entry 2 "Projector x"<-- Devicename "Power Status" <--Parameter name 0 <-- current status "On" <-- "1" description "Off" <-- "0" description My initial approach was just based on an SNMP DataSource with ActiveDiscovery. This works okay but then the DataPoint on every instance is just "Status" and I can't set different thresholds depending on the parameter name (afaik). Based on the above examples, I would want different thresholds for Online Status vs. Power Status. Specific question related to this: is there any way to set a DataPoint name and/or DataPoint thresholds based on data from Active Discovery (i.e. instance properties)? Any other ideas for the SNMP approach? The second option I'm trying is using a script-based DataSource where the script returns the proper DataPoint name/values (e.g. "Online Status=1"). In this scenario, I can make different DataPoints with different thresholds depending on the parameter. The issue I run into is that every instance will show all of the possible DataPoints for any instance whether they apply or not. This is slightly better than the previous scenario but we still end up with more noise/confusion than desired. Specific question related to this: is there any way to enable/disable or show/hide DataPoints on a per-instance level based on data from Active Discovery? Any other ideas on the script-based approach? If you've made it this far, thanks for taking the time!125Views2likes5CommentsCRL Monitoring...is it possible?
Hi All I am new to LM and have a question re monitoring CRL expiration dates. We currently monitor for expiring SSL certs (both internal and external) and need to know if it is possible to monitor CRLs too. We manage multiple customers, and an outage was caused recently due to an expired CRL. I would like to avoid these in the future :) Any help is appreciated. Regards26Views0likes1CommentLM Logs SDT
It is possible to put the LM logs module on a resource in SDT, therefore supressing all LM logs alerts on that resource. The isn't a problem when polling via SNMP/WMI etc. because when the issue is resolved in SDT the alert clears. However, with LM logs when the SDT period is over the alert remains it is then processed and an incident is raised. How does everyone else get around this? The plan I currently have is to create a front-end for SDT on another system and then when SDT clears to immediately acknowledge the LM logs alerts. This will actually achieve a number of things for me - forcing users to add details to SDT notes (either via predefined fields), restricting the SDT period and making sure we don't have a number of unnecessary LM logs incidents being raised.31Views2likes1CommentWebsite Downtimes via API
Hi I'd like to use the API to gather information about the availability of my websites. I will have to gather data for monthly and yearly SLA calculation which features the exact downtimes of the website. With these requirements, I don't think the graph data can deliver accurate data enough. So I'm looking into the /website/websites/{webservice_id}/checkpoints/{checkpoint_id}/data API. Getting Data | LogicMonitor The API works fine, but obviously getting all the statuscodes for every check (every minute) for a whole Month, or even year takes a long time and produces a lot of data that I have to crunch. For me, it would be sufficient to get only the data for downtimes, so every status report which is not 1.0. Does anyone know if the API has such a feature? I already ask for only the datapoints, but this would need some additional filtering. params = {'start': start, 'end': end, 'format': 'json', 'datapoints': 'overallStatus' }35Views1like3CommentsNew VMware modules dropped
Did anybody else notice the ~44 new and ~5 updated modules around VMware dropping in the last hour or so? Does anyone know how to implement these new modules? Since there was talk of making the instances into resources I don’t want to just bring them in without knowing how it’s going to mess with my device list (which is tightly bound to billing for us).726Views30likes41CommentsSDTing via API, one source work the other does not
So I've been working on an LM/Jira JSM integration lately.. the native functions did not work for us. And to be quite honest I cannot remember the details but suffice to say that I have a working Custom HTTP Delivery with three URLs for Active, ACK, and Clear alert functions. Now the goal is an automation action on the Jira side to SDT a specific host. So I began by building and testing the call in Postman. Works like a champ.. I can add a DeviceSDT, with a comment using the deviceDisplayName for a period of 1 hour. Exactly what I want in Jira. Build out the automation rule, it's a manual action with no user input. It should add a DeviceSDT to a variable {{deviceHostname}} with variables that are defining epoch time in MS for {{now}}, and an endDateTime of 1 hour.. again in epoch MS format. I test it and nothing happens. Jira reports back an HTTP400. Odd.. so I run the same thing in Postman and it works. Ok remove the variables and replace them with static content, mirroring exactly whats in the Postman payload. Still, 400 error. Stumble across https://webhook.site (which is fabulous for this sort of thing BTW) Nope.. the call/payload from Jira is 100% identical to Postman. Same Bearer token, and mostly the same headers; content-type, accept-encoding, Accept, Connection and User-Agent. Postman does add a couple that are unique to it but I have not found any doc on what (if any) headers other than Authorization, are required for this SDT call. So does anyone here have any suggestions? I do have a case open with LM support as well as Atlassian. Thanks!96Views2likes39Comments