Bug 1011882 - No possibility to set protocol for syslog-handler through CLI/Management API
Summary: No possibility to set protocol for syslog-handler through CLI/Management API
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Logging
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: EAP 6.3.0
Assignee: James Perkins
QA Contact: Nikoleta Hlavickova
Russell Dickenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-25 10:23 UTC by Ondrej Lukas
Modified: 2014-09-16 17:07 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2014-09-16 17:07:01 UTC
Type: Feature Request
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFCORE-109 0 Major Open Update syslog handler attributes 2017-08-07 08:37:00 UTC

Description Ondrej Lukas 2013-09-25 10:23:03 UTC
Only default UDP protocol is used for syslog-handler. There is no possibility to set TCP/TLS through CLI/Management API. Functionality has been implemeted yet but it couldn't be set by users.

Comment 1 Brian Stansberry 2013-09-25 15:07:15 UTC
Is this a problem in the /core-service=management/access=audit resource tree as well, or just in subsystem=logging?

Comment 2 Ondrej Lukas 2013-09-26 04:46:53 UTC
Problem is only in subsystem=logging syslog-handler.

CLI commands and output:
/subsystem=logging/syslog-handler=syslog:add()
/subsystem=logging/syslog-handler=syslog:read-resource(recursive=true)
{
    "outcome" => "success",
    "result" => {
        "app-name" => undefined,
        "enabled" => true,
        "facility" => "user-level",
        "hostname" => undefined,
        "level" => "ALL",
        "port" => 514,
        "server-address" => "localhost",
        "syslog-format" => "RFC5424"
    }
}

There is no attribute for protocol.

Comment 7 James Perkins 2014-09-16 17:07:01 UTC
This will not be done for EAP 6, but I will target EAP 7 for this. The current way in EAP 6 will be to use the syslog handler as a custom-handler.


Note You need to log in before you can comment on or make changes to this bug.