Forum Discussion
I'm in a multi-tenant IaaS windows environment and I'll need to test my second hop authentication to make sure I can get to the servers we're monitoring from the Collector. The External alerting documentation specifically says it runs the script on the collector. As that is the case, I would imagine the script can do anything you could normally do in the script on that collector.
Caveat from the documentation: "You can only have one External Alert entry per Collector." If you had multiple scripts you wanted to be able to run, they'd need to be tokenized, then pushed through a communication script that starts the pertinent script on the collector which then performs the corrective action on the client. With that in mind, I'd like to rally for an external alerting method that would allow the Collector assigned to a device to be passed as a token that can be used to define where a common script would run from to be able to reach the client VM. I also would like them to be able to be a stage in an escalation... potentially using output from the script to inform the escalation chain somehow. At minimum a true/false continue escalation return flag.
Related Content
- 7 years ago
- 18 days ago
- 6 months ago
- 3 months ago