-
Notifications
You must be signed in to change notification settings - Fork 305
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
Support all attribute names in set-log-attributes #321
Comments
How about an asadmin command to reread logging.properties? |
Also possible - but it would mean that you could not remotely administer the domain unless you had ssh access to the host or at least direct access to the filesystem. |
Very true |
Pandrex247
pushed a commit
to Pandrex247/Payara
that referenced
this issue
May 4, 2021
[Enterprise] FISH-1158 OpenAPI document creation failed when using @Schema annotation with Enum missing a nullcheck
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The set-log-attributes and set-log-levels is almost enough to manage the logging properties for payara instance. Unfortunately set-log-attributes restricts the allowable keys to a set of known values, thus hindering the ability to use new logging properties (i.e. we route our messages over GELF to Logstash). To set these properties we need to modify the logging properties directly on the filesystem and restart payara. It would be much easier if set-log-attributes could allow the setting of any key. As then the logging could be completely configured via asadmin.
The text was updated successfully, but these errors were encountered: