Hi team,
Recently we configured a notification receiver in our AKS cluster and firewalled it off so that only bitbucket can talk to it. Now I have a requirement to allow New Relic also to talk to it so that we can monitor the receiver endpoint from New Relic with connectivity checks and be alerted if the receiver stops responding so that we can know bitbucket requests aren't making it through.
I wanted to ask if there is any guidance for endpoints we can hit from New Relic or payloads we can use to determine whether the receiver is functional without triggering a reconciliation?
If not, would it be possible to add some sort of a dry run hook to the receiver so that we could send normal requests from New Relic that looks like the payloads from whichever git provider (bitbucket in my case) but with an extra query string parameter to make the receiver not action the request other than to reply that it received it?
Something like GET /hooks/my-hook-endpoint/?dry-run=true with a payload that looks like a bitbucket payload with a bitbucket receiver should cause a successful response from the receiver and a log entry in the pod logs, but not cause it to trigger the reconciliation.
Hi team,
Recently we configured a notification receiver in our AKS cluster and firewalled it off so that only bitbucket can talk to it. Now I have a requirement to allow New Relic also to talk to it so that we can monitor the receiver endpoint from New Relic with connectivity checks and be alerted if the receiver stops responding so that we can know bitbucket requests aren't making it through.
I wanted to ask if there is any guidance for endpoints we can hit from New Relic or payloads we can use to determine whether the receiver is functional without triggering a reconciliation?
If not, would it be possible to add some sort of a dry run hook to the receiver so that we could send normal requests from New Relic that looks like the payloads from whichever git provider (bitbucket in my case) but with an extra query string parameter to make the receiver not action the request other than to reply that it received it?
Something like
GET /hooks/my-hook-endpoint/?dry-run=truewith a payload that looks like a bitbucket payload with a bitbucket receiver should cause a successful response from the receiver and a log entry in the pod logs, but not cause it to trigger the reconciliation.