azia1
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: External tool - CLEAR events not being sent when disabling instance/deleting resources
OH ya this problem does exist. Would be great if there was an option thatallowed auto-resolve in SNOW on instance/resource deletion (maybe on the group level using a property?) Currently we handle the orphaned tickets by running a daily script that resolves the ticket, when there are tickets that are open in SNOW on instances/resources that dont exist in LM. As we are a large MSP, this happens in the hundreds daily However if this solution is added it would be one less script running that does bulk admin cleanup. As much as that script helps, it leaves a path for messups,.1View0likes0CommentsRe: Give roles the ability to manage specific role groups
Amen to that We have a number of customers with their own groups, and they actively like to add and remove user access since they have many contractors coming in and out. They keep hammering us with daily changes in user access. If we could designate limited role management, that would save us a ton of admin overhead. I currently have a work around by having a server page that runs a script based on a form, per customer group which I have handed to each of them. But that is a very janky way of doing it, it doesnt look nice or OFFICIAL, plus it still has an admin level apikey stored inside the webpage code(even if its obfuscated). But even this doesnt fully cover everything despite the automation. Manual intervention is often required.0Views0likes0CommentsAdding/Modifying Device System and Auto Properties via API
When I was checking the api documentation, there was nothing there indicating how to add/modify System Properties for example "system.sysinfo". Is this even possible? I bring up as it would be useful for reporting/dashboard purposes, as sometimes we DONT have a means to fully monitor a machine aside from pinging it and or engaging it via an API, but say in a quick report we want to see how many windows/CentOSservers we have and the connection trends, we can sort/filter by system.sysinfo or other system properties that are usually there.Solved87Views0likes4CommentsRe: Status Code for Webchecks
2 hours ago, Stuart Weenig said: Yeah, that's not likely to change. Giving someone the ability to run their code on our point of presence on the internet, could have huge legal ramifications. Even when there is a trusting relationship involved. Doing the standard external webcheck is fine, and really all we need for this scenario, just that the the HTTP Status Code data isn't outputted and displayed. We don't want to run custom code for this (not in our environment/s nor in LM point of presence), that is what we are trying to minimize. Unfortunately, due to the lack of HTTP Status Code outputwe are forced to do run custom code in an everincreasingly unmaintainable amount of datasources in VMs across our and customer environment. Apologies for my previous words causing the misunderstanding about us wanting to run custom code on LM.7Views0likes0CommentsRe: Request to improve the alert rules resources/instances selection options
Oh this would definitely be helpful for our junior admins and admins in general. I made a slight workaround to this, which is very useful if the number of devices covered by the alert rule is very high. 1) Download the relevant devices (with Device name and Device ID, etc) in a csv 2) Added column for where I indicate to follow the alert rule or not (leave empty if not) and save 3) Make a script withBASH/powershell/python/go/etc and import the CSV and filter it only have the items where the last column indicator is not empty 4) Make a Foreach, and have it run on Device ID 5) In the Foreach, utilize the SDK or API calls to PATCH the devices, and add a property like alert.rule with the valuesomerule 6) And then proceeded to create the Alert rules I needed based by specifying the property All this scripting and coding wouldn't be as necessary though if we had the option as you stated, especially if scripting is not a strong point for the admins involved.4Views0likes0Comments