Your data. Anywhere you go.

New Relic for iOS or Android


Download on the App Store    Android App on Google play


New Relic Insights App for iOS


Download on the App Store


Learn more

Close icon

New Relic alerts not working with google chat


#1

I tried post to the google chat webhook, I am getting the following error:
{
response:200,
Unable to invoke Webhook. Webhook responded with HTTP status code 400.
}

Would appreciate some assistance here! Thanks :slight_smile:


#2

Hi there @dexter.yan -

Sorry to hear about the trouble with your webhook! This is a frequent issue, but a wide variety of factors could be at play. We just put together a new guide with some recommended steps for troubleshooting this exact error message:

It would be fantastic if you could take a look and let us know if that leads you down the right path.


#3

Did you make it work??

Thanks


#4

I too am eager to hear a success story here, @dexter.yan! Let us know where you are at with this! :blush:


#5

I would also love to see this get fixed. I’ve tried countless variations of customizing the payload with no success. I’ve captured the request using RequsetBin and replicated the request using Postman. Postman DID work and I was able to see the alert hit Google Chat. The only thing that I did not know how to replicate was the “Host” header entry. In RequestBin, it looked like this: “Host: requestbin.fullcontact.com”. When I used the same value from Postman, the request was rejected. If I excluded the header field all together, it worked. And if I changed the header to be “Host: chat.googleapis.com”, it also worked. What I don’t know is what value New Relic uses for that header when making the call to Google Chat. That is the only thing that I can find that might be the culprit.

New Relic, please fix this!!


#6

Hey there, @eric_flynn! We are currently trying to pinpoint if this is an easy fix or not. Yours is a story we have heard before: trying multiple variations to no prevail—pretty crazy-making. If I can be totally candid: we consider this issue to be caught somewhere between a bug and feature request. Like you mentioned above, it should work! But doesn’t because Google is rejecting our formatting in some cases which makes this complex.

Thank you for your patience! I hope to have an update to share when our Alerts experts come back to me with some more concrete answers.


#7

Some news ? In one month we need to adopt google chat.


#8

Hey @sys-admin - We don’t have an update right now - The issue here is the format of JSON that google chat expects does not match that which our Webhook channel sends.
I’ll get your +1 added to the feature request here.


#9

Hello, we are also moving to Hangout Chat next month, let me know if you need any help from google to fix this.


#10

Hey @jeetendra.po - Thanks for your additional +1 here, I’ll get that added and passed over to the Alerts team.


#11

Hello, we are also moving to Hangout Chat next month, there is update on this ?


#12

Hey @sys-admin - No update right now, your +1 is added though.


#13

Hello, there is any news about this?
Thanks


#14

Hi @mdiasmolina, there is a Feature Idea on this here, if you could vote on it and add your use-case that would be great, as the more support these features get the better :slight_smile:


#15

Hello, we’ve change to Google Chat but the New Relic alert notifications are on the old platform, there is update on this?


#16

Hey @Vinicius.Peres - no update right now, but we can definitely get your +1 added :slight_smile: Feel free to vote over on the Feature Idea here: