Uptime monitoring wrongly reports 200 error code when the API fails #97835
Description
Environment
SaaS (https://sentry.io/)
Steps to Reproduce
Setup Uptime Monitoring on an API that sometimes fails with HTTP 500 errors.
Expected Result
Uptime monitoring should report the correct error code when testing an API
Actual Result
Uptime monitoring reports an HTTP code 200 when the API is returning HTTP 500 for all calls.
When in the logs of my server I can see: (logs in UTC)
172.16.0.4 - - [14/Aug/2025:09:36:12] "GET /api/v1/item/689a073e76e4d04870f83f5c/tiles HTTP/1.1" 500 142 "" "SentryUptimeBot/1.0 (+http://docs.sentry.io/product/alerts/uptime-monitoring/)"
Using Curl also shows the 500 error that Uptime monitor should be reporting:
curl -v "https://app.nimbusimage.com/girder/api/v1/item/689a073e76e4d04870f83f5c/tiles" -H "Girder-Token: "
* Host app.nimbusimage.com:443 was resolved.
* IPv6: (none)
* IPv4: 54.161.172.42
* Trying 54.161.172.42:443...
* ALPN: curl offers h2,http/1.1
... TLS log ...
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://app.nimbusimage.com/girder/api/v1/item/689a073e76e4d04870f83f5c/tiles
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: app.nimbusimage.com]
* [HTTP/2] [1] [:path: /girder/api/v1/item/689a073e76e4d04870f83f5c/tiles]
* [HTTP/2] [1] [user-agent: curl/8.15.0]
* [HTTP/2] [1] [accept: */*]
* [HTTP/2] [1] [girder-token: ]
> GET /girder/api/v1/item/689a073e76e4d04870f83f5c/tiles HTTP/2
> Host: app.nimbusimage.com
> User-Agent: curl/8.15.0
> Accept: */*
> Girder-Token:
>
* Request completely sent off
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
* TLSv1.3 (IN), TLS handshake, Newsession Ticket (4):
< HTTP/2 500
< content-type: application/json
< server: Girder 3.2.8
< date: Thu, 14 Aug 2025 09:54:58 GMT
< allow: DELETE, GET, HEAD, OPTIONS, PATCH, POST, PUT
< girder-request-uid: 5ea1e59d-f6cb-4dd2-b604-fe92f032a7f4
< content-length: 142
< set-cookie: SERVER=s0; path=/
<
* Connection #0 to host app.nimbusimage.com left intact
{"identifier": "girder.utility.assetstore.file-path-not-available", "message": "This assetstore does not expose file paths", "type": "girder"}%
Let me know if I can provide more information to help solve the issue.
Product Area
Alerts
Link
DSN
No response
Version
No response