Rate limit headers missing

[vital tiger]

I wanted to add checks that we aren't hitting our rate limits using the headers listed in the documentation (https://docs.sentry.io/api/ratelimits/). It seems though that we aren't getting these headers when using the cron monitor checkin endpoint. Are these headers not present for cron monitor checkins?

When I dump the headers into our logs on our webserver, this is what I see:

{'server': 'nginx', 'date': 'Thu, 11 Apr 2024 17:28:10 GMT', 'content-length': '0', 'access-control-allow-origin': '*', 'vary': 'origin,access-control-request-method,access-control-request-headers', 'access-control-expose-headers': 'x-sentry-error,x-sentry-rate-limits,retry-after', 'cross-origin-resource-policy': 'cross-origin', 'strict-transport-security': 'max-age=31536000; includeSubDomains; preload', 'via': '1.1 google', 'alt-svc': 'h3=\":443\"; ma=2592000,h3-29=\":443\"; ma=2592000'}

[high atlas]

Hi there,

I saw your other post. It looks like you're using the ingest endpoints which are not rate limited in this way. Those rate limit headers will appear on any of our APIs that respond from the Django part of our application and are usually involved in various CRUD operations. Check-ins would not be part of this.

My colleague is looking into your other question.

[vital tiger]

Okay great, thank you for that information!

[high atlas]

No problem! I had a question about where you're seeing those headers in your server logs - is this from a check-in? Does that check in use the ingest endpoint?

[vital tiger]

Yes, that's from a check-in like the one posted in the other thread (i.e. like https://o415829.ingest.sentry.io/api/XXXXXXXXXX/cron/d61e4e18-1b7e-405f-9581-50d7f3f43b6d/XXXXXXXXXX/?check_in_id=7475e911-8aeb-4b0f-8715-70f89129ac28&status=ok&environment=production). The specific headers above were for: monitor d61e4e18-1b7e-405f-9581-50d7f3f43b6d (checkin 6004ead0-6164-4b30-ac60-f6a638b23b1a).

[high atlas]

thank you!

[fervent zinc]

@high atlas sounds like a relay bug (?) to me.