简体   繁体   English

带有 jboss 的 Keycloak 调试级别日志杂乱无章

[英]Keycloak debug level logs with jboss are cluttered

I am using jboss/keycloak:15.0.2 .我正在使用jboss/keycloak:15.0.2 To comply with security requirements, I need to enable DEBUG level logs to log success messages for user login.为了符合安全要求,我需要启用 DEBUG 级别的日志来记录用户登录的成功消息。 The docker compose config looks like docker 组合配置看起来像

  loginservice:
    image: my-image
    environment:
    - KEYCLOAK_IMPORT=/tmp/realm-export-deploy.json
    - KEYCLOAK_USER=admin
    - KEYCLOAK_LOGLEVEL=DEBUG
    - KEYCLOAK_PASSWORD_FILE=/run/secrets/loginadmin
    - SYS_PROPS=-Dkeycloak.migration.strategy=IGNORE_EXISTING
    - PROXY_ADDRESS_FORWARDING=true
    - KEYCLOAK_FRONTEND_URL=https://servername.net/keycloak/auth
    ports:
    - 7070:8080

However, as soon as the service comes up the logs are getting cluttered with repeated messaging of但是,一旦服务启动,日志就会变得杂乱无章,重复的消息

08:00:30,986 DEBUG [org.keycloak.services.scheduled.ScheduledTaskRunner] (Timer-2) Executed scheduled task AbstractLastSessionRefreshStoreFactory$$Lambda$2097/0x0000000841707840
08:00:35,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) new JtaTransactionWrapper
08:00:35,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) was existing? false
08:00:35,985 DEBUG [org.keycloak.models.sessions.infinispan.changes.sessions.PersisterLastSessionRefreshStore] (Timer-2) Updating 0 userSessions with lastSessionRefresh: 1639123175
08:00:35,986 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper  commit
08:00:35,986 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper end
08:00:35,986 DEBUG [org.keycloak.services.scheduled.ScheduledTaskRunner] (Timer-2) Executed scheduled task AbstractLastSessionRefreshStoreFactory$$Lambda$2097/0x0000000841707840
08:00:40,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) new JtaTransactionWrapper
08:00:40,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) was existing? false
08:00:40,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper  commit
08:00:40,986 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper end
08:00:40,986 DEBUG [org.keycloak.services.scheduled.ScheduledTaskRunner] (Timer-2) Executed scheduled task AbstractLastSessionRefreshStoreFactory$$Lambda$2097/0x0000000841707840
08:00:45,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) new JtaTransactionWrapper
08:00:45,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) was existing? false
08:00:45,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper  commit
08:00:45,985 DEBUG [org.keycloak.transaction.JtaTransactionWrapper] (Timer-2) JtaTransactionWrapper end

The events I enabled from keycloak UI:我从 keycloak UI 启用的事件: 在此处输入图像描述

Any clue whats up with the clutter and how can it be disabled?任何线索是怎么回事杂乱,它怎么能被禁用?

You don't need to enable DEBUG logs for all Keycloak packages.您不需要为所有 Keycloak 包启用调试日志。 Just enabling it for org.keycloak.events is enough.只需为org.keycloak.events启用它就足够了。 This can be done by adding this JBOSS startup script to the Keycloak container:这可以通过将此 JBOSS 启动脚本添加到 Keycloak 容器来完成:

embed-server --server-config=standalone-ha.xml
/subsystem=logging/logger=org.keycloak.events/:add(category=org.keycloak.events,level=DEBUG)
stop-embedded-server

This will capture most of the relevant events in the logs.这将捕获日志中的大部分相关事件。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 在 Serilog 中仅显示调试级别日志 - Show only debug level logs in Serilog 在调试级别写日志最合理的地方在哪里? - Where is the most reasonable place to write logs at a debug level? 在调试级别从Spring集成日志中删除有效负载 - Remove payload from spring integration logs in debug level 当Kafka lib用作Keycloak模块时如何停止Kafka DEBUG日志 - How to stop Kafka DEBUG logs when Kafka lib is used as Keycloak module Keycloak中缺少审核日志 - Missing Audit Logs in Keycloak 将来自现有log4j附加程序的日志将调试级别为“错误”或更高级别的所有日志写入rsyslog - Write logs from existing log4j appenders all logs with debug level “error” or higher to rsyslog 即使我将日志级别设置为调试级别,Go 中的 Zap 包也会打印所有日志 - Zap package in Go prints all logs even I set log level as Debug level 的logback <logger> 日志来自jboss-logging时忽略级别 - logback <logger> level ignored when logs come from jboss-logging Jboss 7.2 根记录器级别 DEBUG 在执行 jpa 查询时引发 ConcurrentModificationException - Jboss 7.2 root-logger level DEBUG provokes ConcurrentModificationException on executing a jpa query Log4j2.xml配置关闭休眠调试级别的日志 - Log4j2.xml configuration to turn off hibernate debug level logs
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM