Closed cdelst closed 1 year ago
Assigning to @getsentry/support for routing, due by (sfo). ⏲️
Routing to @getsentry/product-owners-settings-integrations for triage, due by (sfo). ⏲️
@cdelst So it looks like your service is returning a 404 based on the Integration dashboard.
Something at that endpoint is returning a 404. My guess is that something in your routing is messed up so it doesn't reach the route you expect.
Thank you! That's useful information.
Figured it out, thanks.
Surfacing the webhook logs in-app would be super useful if there's something I can +1 to support that feature for 👍🏻
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Expected Result
When errors are sent to sentry, I expect the error webhook to hit the webhook URL designated in the integration.
Actual Result
We are not seeing any requests made from Sentry to the endpoint specified in the Webhook URL field, as far as we can tell.
I designated
https://ld-stg.launchdarkly.com/sentry/webhook
as our webhook route, and looking at the logs for that route after sending ~70 errors to sentry, I am not seeing any requests.This is a chart displaying the amount of requests made to our ingestion endpoint (the 1 being me sanity-checking our logging with a manual request)
For some more background information, we're relying on the
Sentry-Hook-Resource: error
header to route the request correctly in our ALB.We validated that our ALB is working correctly by running two different curl commands:
cc @Dhrumil-Sentry
Product Area
Issues
Link
https://launchdarkly-ecosystem.sentry.io/settings/developer-settings/launchdarkly-staging/
DSN
No response
Version
No response