ContributionsMost RecentMost LikesSolutionsRe: Bulk add of monitored instance - Ping (Multi)- I won’t say it was the best result, but it worked for the concerns I have. End result was to clone the PingMulti- datasource and modify it to only apply to a custom hasCategory that is attached to any collector needed. The groovy script is a very ugly line by line entry: println("<ip1>" + "##" + "<description1>") println("<ip2>" + "##" + "<description2>") return 0 Reasoning was to give myself a neatly formatted list I could quickly skim and edit vs a messy array and loop or single use CSV. Having this info in a datasource also lets me replace, change or add collectors as monitor points with only needed the single system category and the list itself not be device dependent. I think Joe’s answer would have worked well enough but the environment and target devices we ping change just often enough or require multiple collectors to check. Re: Bulk add of monitored instance - Ping (Multi)- What about cloning the datasource to a new one dependent upon a custom system category applied to the appropriate targets and having the IP’s in an array built into the script giving a central management point for what in my case is a pretty long list? Bulk add of monitored instance - Ping (Multi)- I have been tasked with adding a large number of ping only monitored instances. Is there so way to automate this process similar to the csv file for adding resource/devices? Re: Alerting for switch port traffic drop using interface description I think I might actually just take a page from https://community.logicmonitor.com/product-discussions-22/creating-a-complex-data-source-to-check-the-interface-description-and-then-the-state-of-an-interface-to-generate-an-alert-2872 and adjust the existing datasource and add a custom data point to include in a top level alert. Now to figure out how to go about mangling that process. Alerting for switch port traffic drop using interface description I’m trying to manufacture a health check for a security camera system that doesn’t offer any internal checks. The cameras can fail but still respond to ping and other basic checks, so my thought is to look at the switches and use the port descriptions (which we manually maintain) and create a alert for only those ports if traffic falls below a threshold indicating there is no stream to the NVR. All of the ports connected to cameras have ‘SecCam’ followed by location info in the description which I can see under the Switch / Network Interfaces for: system.instanceDescription auto.interface.alias auto.interface.description How would I go about setting up monitoring in a central way? Currently we’re manually creating an Instance group and putting interfaces in it per switch but that’s still dozens or possibly hundreds of different places to manage alert tuning / SDT. Solved
Top ContributionsBulk add of monitored instance - Ping (Multi)-Re: Bulk add of monitored instance - Ping (Multi)-Alerting for switch port traffic drop using interface descriptionSolvedRe: Bulk add of monitored instance - Ping (Multi)-Re: Alerting for switch port traffic drop using interface description