[jboss-jira] [JBoss JIRA] (WFCORE-4332) JBoss provided syslog handler should support <named-formatter>
James Perkins (Jira)
issues at jboss.org
Mon Feb 18 12:17:04 EST 2019
[ https://issues.jboss.org/browse/WFCORE-4332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
James Perkins updated WFCORE-4332:
----------------------------------
Summary: JBoss provided syslog handler should support <named-formatter> (was: JBoss provided syslog handler should support <pattern-formatter>)
> JBoss provided syslog handler should support <named-formatter>
> --------------------------------------------------------------
>
> Key: WFCORE-4332
> URL: https://issues.jboss.org/browse/WFCORE-4332
> Project: WildFly Core
> Issue Type: Feature Request
> Components: Logging
> Reporter: Ranjith Pulluru
> Assignee: James Perkins
> Priority: Major
> Labels: Previous_RFE, logging
>
> 1. Proposed title of this feature request
> JBoss provided syslog handler should support <pattern-formatter>
> 2. Who is the customer behind the request?
> Account name: Glockle Direct GmbH (911672)
> Customer segment: 3
> TAM : no
> SRM : no
> Strategic: no
> 3. What is the nature and description of the request?
> From JBoss EAP 6.2+ onwards we provided JBoss syslog handler. By using the JBoss syslog handler customer can use only syslogType `RFC3164, RFC5424`.
> customer doesn't have option to change the pattern of syslogType.
> 4. Why does the customer need this? (List the business requirements here)
>
> By using the JBoss provided syslog handler and the syslogType customer cannot print the thread-id, class name in log file.
> 5. How would the customer like to achieve this? (List the functional requirements here)
> <syslog-handler name="SYSLOG">
> <app-name value="JBoss"/>
> <level name="INFO"/>
> <server-address value="localhost" />
> <facility value="local-use-6"/>
> <formatter>
> <pattern-formatter pattern="%d{HH:mm:ss,SSS} %-5p [%c] (%t) %s%E%n"/>
> </formatter>
> </syslog-handler>
> 6. For each functional requirement listed in question 5, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
> 7. Is there already an existing RFE upstream or in Red Hat bugzilla?
> No
> 8. Does the customer have any specific timeline dependencies?
> No
> 9. Is the sales team involved in this request and do they have any additional input?
> No
> 10. List any affected packages or components.
> logging jboss-logging
> 11. Would the customer be able to assist in testing this functionality if implemented?
> Yes
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the jboss-jira
mailing list