Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable HTTP request log (access log) in Production #1498

Closed
tatu-at-datastax opened this issue Oct 4, 2024 · 0 comments · Fixed by #1503
Closed

Enable HTTP request log (access log) in Production #1498

tatu-at-datastax opened this issue Oct 4, 2024 · 0 comments · Fixed by #1503
Assignees

Comments

@tatu-at-datastax
Copy link
Contributor

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"

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:

  1. Enable in application.yaml for all envs (although could also disable for tests, via src/test/resources/application.yaml to reduce noise)
  2. Enable via deployment (Helm Chart) by ENV QUARKUS_HTTP_ACCESS_LOG_ENABLED.

Unless there are specific reasons not to, I am leaning towards (1).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant