Recent Discussions
Event Sources SNMP and Windows collectors?
I have little personal experience with Event Sources, to my knowledge we dont extensively use them on our portal. I've found about 3 documents pertaining to event sources, and I'm trying to find out whether or not a Windows collector can even get SNMP traps? The documentation I've found doesnt even discuss about how to set up the other side to get into LM ... do we need to set up credentials on the snmp collector to allow snmp to be delivered? Or can the collector just see snmp traps on the right ports? Or does the OS not even let that through? I cant find these details anywhere. I'm just wondering if maybe I've overlooked that discussion, or if LM just figured out its a dumb question and I should know. :) Anyway I have a device that can only send email or snmp traps, but our collector base is mostly windows, and we use WMI obviously for monitoring, so nothing SNMP related is even set up on any windows servers. Sorry if this is a dumb question. Help? :)SolvedLewis_Beard2 days agoExpert
20Views0likes2Comments
cvl14 days agoNeophyte
39Views2likes3CommentsWhich property source sets system.collector?
I realized I have several windows collectors that have system.collector set to false for some reason, and I cant figure out why. Because they are definitely collectors. I hate to ask such a basic question but does anyone know which PropertySource sets that? I looked through the Device_BasicInfo code, and I didnt see it. Maybe I missed it. Maybe its upstream from Device_BasicInfo, because I do see Device_BasicInfo referring to some other system properties as part of its logic, from the host properties. I need to figure out why I have a bunch of collectors, in my collector section, that monitor themselves, have valid links to themselves in the resource tree, but on the resource tree, system.collector is false. But on some it is true. Thanks!SolvedLewis_Beard16 days ago24Views0likes3CommentsAuto Balanced Collector Group vs Failover?
Hi, I'm wondering if there are pros and cons vs setting up multiple collectors as an ABCG vs stand-alone collectors with failover. If we have two collectors in the same location, monitoring the same servers, I'd use an ABCG. However... Let's say I have servers in Los Angeles and New York, and I have one collector in each location. If I set them up as an ABCG, would LM be smart enough to have the LA machines be monitored by the LA Collector and NY by NY, or does it just assign them randomly? I'm not sure if it has each collector ping each device to see which one has a better connection or anything like that. I currently have the LA collector manually assigned to the LA machines. I then have the LA Collector fail over to the NY Collector in the event of a problem. Each location CAN see the other, but I don't want LM monitoring things across the connection when each location has it's own collector on-site. Thoughts?Solved41Views0likes4Comments
LM Servicenow Integration
We have integrated service now with LogicMonior and we see that the Auto resolution of Incidents is not happening even when the Alert is cleared in LogicMonitor. We see that there is no clear even in logs of the integraion even after he alert is cleared which is causing the Incident in open stateSolvedvenkat2 months ago94Views3likes8CommentsAPI v3 Python Patch on user 403 forbidden
I have some old python code (that I didnt write) that uses v1 of the API that does a patch with a super minimal patch data block, just the value needed. Personally, I have Groovy code that does some patching using the retrieved user in a Map object and I make a minimal map with just the stuff v3 requires that I set (which v1 didnt) like roles and password and etc, and I managed to get code working with Groovy v3. But I'm in a circumstance where I have to use python and patch on a user, and for the life of me, I keep getting a 403 forbidden error. I've found several examples online, and basically I believe I've got everything set up correctly, the code is mostly similar to the old working v1 code except it has the changes that v3 needs. But I get a 403 error (forbidden). But I know the API token has rights to update the user (tho it is still attached to a user with an administrator role, but I dont think thats the issue, I have groovy code using the same API token). I hate to ask people to look at code but is there anything obviously wrong here that I'm missing for python and v3? http_verb ='PATCH'; resource_path = '/setting/admins/' + str(user_id); patch_data = '{"roles":[{"name":"myrole"}],"email":"what@whatever.what","username":"blah","password":"meh","apionly": true}'; queryParam = '?changePassword=false&validationOnly=false' url = 'https://'+ Company +'.logicmonitor.com/santaba/rest' + resource_path + queryParam; epoch = str(int(time.time() * 1000)); requestVars = http_verb + epoch + patch_data + resource_path; hmac1 = hmac.new(AccessKey.encode(),msg=requestVars.encode(),digestmod=hashlib.sha256).hexdigest(); signature = base64.b64encode(hmac1.encode()); auth = 'LMv1 ' + AccessId + ':' + signature.decode() + ':' + epoch; headers = {'Content-Type':'application/json','Authorization':auth,'X-Version': '3'} response_patch = lm_session.patch(url, data=patch_data, headers=headers) return response_patch; Thanks!SolvedLewis_Beard2 months ago45Views1like2CommentsResource Tree Deprecation?
I missed the latest the recent virtual Roadmap Roadshow. When reviewing the summary notes from the session, I noticed the following statement regarding the resource tree. ResourceExplorer: Say goodbye to the traditional resource tree! Our new Resource Explorer is designed for modern environments like Cloud and Kubernetes. It leverages metadata and tagging to help you quickly find and visualize resources. I don't see how resource explorer can provide feature parity when it comes to filtering, setting custom/inherited properties, grouping devices, API query refinement etc. If we lose this functionality, the product loses half it's value. Is there anyone in the community that sat in for this session that can provide some more context?SolvedDrelo2 months ago56Views0likes3CommentsModule Toolbox z-index issue
z-index fix needed for the "Module Toolbox" page. See screenshotSolvedDavid_Bond3 months agoProfessor
123Views4likes8Comments
