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
Although #752 was completed months ago, it doesn't look like HTTP request logs are enabled in Production kubes. This is probably because src/main/resources/application.yaml has:
quarkus:
http:
# access log format, must be explicitly enabled
access-log:
pattern: "%h %l %t \"%r\" %s %b"
Although #752 was completed months ago, it doesn't look like HTTP request logs are enabled in Production kubes. This is probably because
src/main/resources/application.yaml
has:and does not have
enabled: true
(which as per https://quarkus.io/guides/http-reference#configuring-http-access-logs is needed, as property quarkus.http.access-log.enabled.And we do not (I think, given there are no entries in Splunk) have matching ENV override (
QUARKUS_HTTP_ACCESS_LOG_ENABLED
) either.There are at least 2 ways we could do this:
application.yaml
for all envs (although could also disable for tests, viasrc/test/resources/application.yaml
to reduce noise)QUARKUS_HTTP_ACCESS_LOG_ENABLED
.Unless there are specific reasons not to, I am leaning towards (1).
The text was updated successfully, but these errors were encountered: