524 Origin Timeout not visible in Analytics view

Example error from our service’s client:

Pushing image to xxxyyy.com/REDACTED
error pushing image: failed to push to destination xxxyyy.com/REDACTED: PATCH https://xxxyyy.com/REDACTED?_state=REDACTED: unexpected status code 524 : <html>
<head><title>524 Origin Time-out</title></head>
<body bgcolor="white">
<center><h1>524 Origin Time-out</h1></center>
<hr><center>cloudflare-nginx</center>
</body>
</html>

Obviously these are requests related to pushing a container image. I’ve verified the related image
is a big one (contains a layer ~ 2G) so I’d say it’s valid the default 100s might not be enough. It’s surprising for me that the error occurs as I’d expect for the communication during the container image layer transfer to be… non-silent (?) from the origin side (at least TCP ACK messages maybe? o.O).

Anyhoo, I’m failing to filter out these particular requests both in Cloudflare (Analytics / WAF) but also these didn’t reach my origin. Our loadbalancers didn’t register these requests, as if Cloudflare didn’t even send any data forward (so how could they timeout?) :expressionless:

There, in general, are 524 s visible in Analytics, but it seems it’s not all of them. Is the traffic sampled and I’m just out of luck? (but again: the origin also didn’t register any such request).

Traffic is indeed sampled. If you need to the full logs, only CF Enterprise plan has access to logpush/pull https://developers.cloudflare.com/logs/about/ and https://developers.cloudflare.com/logs/tutorials/parsing-json-log-data/ and https://developers.cloudflare.com/logs/faq/logpush/

And log fields for HTTP requests available via logpush https://developers.cloudflare.com/logs/reference/log-fields/zone/http_requests/

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.