You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our logs some requests for which the upstream status is 502 have their $uri variable overridden so that when Kong logs this request the log line appears to have /kong_error_handler as the URI. This is seen in the log line below (I have removed some of the log fields).
This is also reflected on the Prometheus metrics since these 502s which appear to originate from the upstream but have the $uri parameter overridden appear on the kong_http_requests_total metric as having the source as kong rather than the service.
It seems that the upstream does NOT return 502 for these requests (the request never reaches the upstream).
Expected Behavior
The URI should match the $uri field should match the request URI (something like api/v1/things). The $upstream_status should not be 502.
Steps To Reproduce
This error happens intermittently and I cannot reproduce it.
Anything else?
We are trying to create alerts based on errors that originate from Kong. However, this bug prevents us from using the kong_http_requests_total metric to create alerts.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Kong version (
$ kong version
)kong:3.4.2-ubuntu
Current Behavior
In our logs some requests for which the upstream status is 502 have their
$uri
variable overridden so that when Kong logs this request the log line appears to have/kong_error_handler
as the URI. This is seen in the log line below (I have removed some of the log fields).Which corresponds to this log format
This is also reflected on the Prometheus metrics since these 502s which appear to originate from the upstream but have the
$uri
parameter overridden appear on thekong_http_requests_total
metric as having the source askong
rather than theservice
.It seems that the upstream does NOT return 502 for these requests (the request never reaches the upstream).
Expected Behavior
The URI should match the
$uri
field should match the request URI (something likeapi/v1/things
). The$upstream_status
should not be 502.Steps To Reproduce
This error happens intermittently and I cannot reproduce it.
Anything else?
We are trying to create alerts based on errors that originate from Kong. However, this bug prevents us from using the
kong_http_requests_total
metric to create alerts.The text was updated successfully, but these errors were encountered: