-
Suggestion
-
Resolution: Won't Do
-
None
-
None
-
None
Logging in flat files is great for standard configurations.
However, when deploying Crowd in large organizations, it's annoying to have a lot of log files to monitor, rotate and backup. Especially when you already have some standard log management processes.
We centralize all logs using the syslog protocol. But in order to send Crowd logs to a syslog server, you currently have to modify a lot of files.
And I let Crowd developpers imagine the mess admins have to deal with when upgrading Crowd... Especially when the logging configuration is updated between releases.
So, when will the admins get a convenient logging feature?
- is related to
-
JRACLOUD-22508 Easier syslog integration
- Closed
-
JRASERVER-22508 Easier syslog integration
- Gathering Interest
- relates to
-
CONFSERVER-21048 Easier syslog integration
- Closed
-
CWD-2086 Implement standardised application logging for Crowd
- Closed
-
CONFCLOUD-21048 Easier syslog integration
- Gathering Interest
Thank you for taking the time to file this issue. Feedback like yours helps us release valuable Crowd features that solve problems for the greater customer base. To that end we aim to add features to Crowd that would best fulfill our customers needs. However at this time, this suggestion is not on the Crowd development roadmap and due to that fact we have decided to close your suggestion.
If you still feel that this issue is still relevant to your needs, please feel free to raise a new issue and link to this one.
If you would like to see how we select features for a new release, please read http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+Policy.