Documentation for centralized logging support (#1636)

* Documentation for centralized logging support

Closes #1635

* Update release_notes/topics/19_0_0.adoc

Co-authored-by: Stian Thorgersen <stian@redhat.com>

* Update upgrading/topics/keycloak/changes-19_0_0.adoc

Co-authored-by: Stian Thorgersen <stian@redhat.com>

Co-authored-by: Stian Thorgersen <stian@redhat.com>
This commit is contained in:
Dominik Guhr 2022-07-28 11:03:11 +02:00 committed by GitHub
parent 564158eddf
commit 7eecc14656
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 12 additions and 0 deletions

View file

@ -87,3 +87,9 @@ spec:
component: keycloak
```
See also the https://kubernetes.io/docs/tasks/run-application/configure-pdb/[Kubernetes Documentation].
= Initial Support for centralized logging
Starting with version 19, Keycloak supports sending logs using GELF to centralized logging solutions like ELK, EFK or Graylog out of the box.
You can find the documentation and examples to get you up and running quickly in the https://www.keycloak.org/server/logging#_centralized_logging_using_gelf[logging guide]

View file

@ -63,6 +63,12 @@ Apart from disabling the /q/ endpoints, these are the other improvements made to
Expect more enhancements in this area in the future.
For more information, see the https://www.keycloak.org/server/health[Health guide]
= Changes using GELF / centralized log management
As stated in the release notes, Keycloak now supports gelf logging for centralized logging systems out of the box.
When you added the gelf related quarkus jars yourself in a prior version, make sure to switch to the supported configuration options in the https://www.keycloak.org/server/logging#_centralized_logging_using_gelf[logging guide] and remove your jars from the `providers` folder.
= Changes affecting developers
{project_name} undergoes large refactoring, which impacts existing code.