[
https://issues.apache.org/jira/browse/SYNAPSE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vanjikumaran Sivajothy updated SYNAPSE-282:
-------------------------------------------
Fix Version/s: (was: 2.0)
FUTURE
> Allow Synapse to consume syslog events
> --------------------------------------
>
> Key: SYNAPSE-282
> URL: https://issues.apache.org/jira/browse/SYNAPSE-282
> Project: Synapse
> Issue Type: New Feature
> Reporter: Andreas Veithen
> Assignee: Andreas Veithen
> Priority: Minor
> Fix For: FUTURE
>
>
> The idea is to use Synapse to consume syslog events. This would open Synapse
> to a range of new use cases in system monitoring.
> The necessary infrastructure to be developed is as follows:
> * A message builder capable of parsing syslog messages as defined in RFC 3164
> and transform them into well defined XML messages that can be easily
> processed with standard Synapse mediators.
> * A UDP transport listener for Axis2. This would be designed as a "raw"
> protocol listener similar to the existing TCP transport ("raw" meaning that
> the message is directly extracted from the UDP payload without an
> intermediate application protocol). This transport would be used to process
> syslog messages from remote hosts.
> * A transport listener capable to receive messages from a UNIX pipe (FIFO).
> Since pipes are streams, the transport listener must be able to split the
> stream into individual messages (potentially using some pluggable algorithm).
> Note that pipes can be accessed using standard Java I/O. This transport would
> be used to process syslog messages from the local host.
> Both transport implementations should be totally independent of the syslog
> protocol so that they could be reused for other purposes.
> An open issue is that syslog events not necessarily contain timestamp/host
> information. If not available it must be added by Synapse. The problem is
> that the transport listeners should be protocol independent and that it is
> not sure that the message has access to the required information (i.e. the
> remote host from which the message was received).
> The target release for this new feature is 1.3 (or the next release after
> 1.2). Given that it has no impact on existing code, it will be included in
> the 1.2 release as experimental feature if the code is sufficiently stable.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
