Repository navigation
Replies: 5 comments 4 replies
|
Hey. To be honest, the current logging impl is more a "better than nothing" v1. I'll start to add more capabilities shortly. I'd focus on json support, and was not sure about syslog, but seems we should also support it. So yes, expect more to come in upcoming versions :) We always try to give the most convenient ux, so would be nice to know what raw quarkus properties you use in the syslog area, and how we could make your life easier, e.g. if some properties could have a good abstraction (we are able to provide e.g. bwtter naming, 1:n mappings)...). I am more than open to input, as I dont have much experience using syslog. |
|
Thanks for your reply. Currently, I'm using this set of properties: So, at least in my usecase I need to set the (Of course, there are more syslog properties at the Quarkus configuration page than the ones I used above, it might be good to support more than only the above mentioned.) |
|
In #9592 (reply in thread) @stianst mentioned the use of Yes, I kind of extend Keycloak with the syslog logging capabilities of Quarkus, but I also need to configure this for various envs with specific values. |
|
Should this be closed now that #10414 was closed too? |
|
@dasniko atm we think about letting people use quarkus.properties directly instead, meaning without the gate of "everything is a build time property" to support edge cases like this. I guess that would solve your problem? |
|
Yeah, great news. This would indeed solve my issue! 👍 |
|
One more question... Will it only be possible via |
|
@DGuhr any progress on this? |
Uh oh!
There was an error while loading. Please reload this page.
Hi @DGuhr
in one of my customer-projects, we are using Syslog logging with Keycloak.
I got it working with native Quarkus properties in
conf/quarkus.propertieslike suggested in the docs. Works.Unfortunately, I cannot overwrite any of the Quarkus properties at runtime, as this seams to be a build time config. But there is at least the
quarkus.log.syslog.endpointproperty, which I want to set dynamically in the various environments to different values, or even switch it off withquarkus.log.syslog.enable=false. While I'm in a Docker container, I try to set the overwrites via environment variables (uppercase letters and_instead of..But this doesn't work, only the build-time properies get into count.
Do you have any suggestions, workarounds or even fixes for upcoming versions?
All reactions