We all know that old philosophical question: if vRealize Operations sends a REST call to Orchestrator that is inherently invalid, was it ever really sent? It’s a question as old as time. Luckily John Dias has a work around to help keep things flowing. He directs the vRealize Operations call to a web server using Webhook Shims for Log Insight and vRealize Operations. This then translates the call into something Orchestrator will recognize as valid.
This is just the first of an ongoing series, he’s moving next onto remediation techniques once these problem notifications are received. Some very interesting stuff, wish you didn’t have to jump through so many hoops thought!
If you are a user of vR OPs, you know that it can monitor your infrastructure, server OS, applications and more. But as this commercial suggests, monitoring is only part of the answer. Wouldn’t it be much better to have vR Ops attempt some simple fixes before giving up and calling for human intervention?In this blog post series, I will explain how to activate a vRealize Orchestrator workflow based on a vR Ops alert to fix an issue instead of just alerting you.