VMware Cloud Community
billdossett
Hot Shot
Hot Shot
Jump to solution

trouble shoot sending alerts from vROPs

Hi, we have a new HCI infrastructure with all the bells and whistles.

I don't know much about vRealize - but it looks to me like vRealize Operations collects all the alerts from vSphere and NSX - I need to be able to send alerts to our enterprise monitoring framework with a webhook.

So, I configured an alert that fires when a host is put in maint mode for simple test.  The alert is defined, it calls a notification that I have defined.  The notification has a outbound method and a payload associated with it.

I put the host in maint mode, I see the alert in troubleshooting - it is active, but nothing is received at the monitoring collector.

I have taken all the info that I configured and put it in a curl command and when I login to the shell of the appliance, I use the curl command and it works perfectly - so connectivity between the appliance and our collector is not an issue...

I have found and have been digging in the support logs and all over, but I can't seem to find any info on what is happening.  The alert fires... but from there on in,  I can't figure out anyway of monitoring what is happening, is it sending the webhook info out?  I am not seeing it hit our monitoring system at all - as I do with the curl, so I am inclined to think it is not sending the webhook...  Any advice on how to trouble shoot this?  If I can get it to work it would be a big integration for me and all our monitoring people would be happy...  

thanks

Bill'

Bill Dossett
Reply
0 Kudos
1 Solution

Accepted Solutions
billdossett
Hot Shot
Hot Shot
Jump to solution

so, I setup postman as a reverse proxy and in outbound settings I created a proxy.

changed endpoint to http and I can now see the requests with body headers and all and it looks fine... so that is the answer for seeing what is coming out of vrops alert...  the problem is that it is http, so when the proxy does its thing it gets a 404 and isn't accepted by our monitoring framework.

I followed the instruction for doing https inspection and installed open ssl so postman could use it, which all looks ok, but when I try to set my outbound proxy to https and save it, it gets the certificate, asks if it should save it and then just loops around and around asking if I should accept and save the certificate which I do over and over and it never seems to save it... it is saved, but  ti doesn't work, I get nothing at my postman proxy...  but anyway, postman proxy is a great way to see what is coming out of a blackbox api calls.  I will post another question to see if anyone knows about the https problem.

Bill Dossett

View solution in original post

Tags (1)
Reply
0 Kudos
2 Replies
billdossett
Hot Shot
Hot Shot
Jump to solution

so, I setup postman as a reverse proxy and in outbound settings I created a proxy.

changed endpoint to http and I can now see the requests with body headers and all and it looks fine... so that is the answer for seeing what is coming out of vrops alert...  the problem is that it is http, so when the proxy does its thing it gets a 404 and isn't accepted by our monitoring framework.

I followed the instruction for doing https inspection and installed open ssl so postman could use it, which all looks ok, but when I try to set my outbound proxy to https and save it, it gets the certificate, asks if it should save it and then just loops around and around asking if I should accept and save the certificate which I do over and over and it never seems to save it... it is saved, but  ti doesn't work, I get nothing at my postman proxy...  but anyway, postman proxy is a great way to see what is coming out of a blackbox api calls.  I will post another question to see if anyone knows about the https problem.

Bill Dossett
Tags (1)
Reply
0 Kudos
billdossett
Hot Shot
Hot Shot
Jump to solution

so, when setting up an alert, there is the outbound instance where you can put your endpoint, then also in the payload there is a header field to put your endpoint URL.

Don't use them both!!!  if you do, then it just concatenates the two URLs, which are the same... into one URL and  it obviously does not work.

I was able to determine this by using postman as proxy and seeing the URL come in and you could easily see the URL was two URLs concatenated... so that mystery is also cleared up.  

I read a number of docs about setting up alerts, but none that I found explained why there was a URL field in both the outbound instance and in the payload header...  Not sure if I missed it somewhere, but I looked pretty thoroughly.

Bill Dossett
Reply
0 Kudos