Re: syslog
Here is the translated question. "Using netty to receive udp messages using unmashal().syslog() to parse Chinese message， I got the error encoded message, how should I solve？" I think it more like an encoding error, and we need more detail context information. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Feb 28, 2022 at 2:31 AM Andrea Cosentino wrote: > > Please, can you translate to English? > > Il dom 27 feb 2022, 19:17 花儿与少年， <86744...@qq.com.invalid> ha scritto: > > > 使用netty接收udp消息使用unmashal().syslog()解析中文乱码，应该如何解决
Re: syslog
Please, can you translate to English? Il dom 27 feb 2022, 19:17 花儿与少年， <86744...@qq.com.invalid> ha scritto: > 使用netty接收udp消息使用unmashal().syslog()解析中文乱码，应该如何解决
syslog
nettyudpunmashal().syslog()??
Re: Hoe to get camel-quarkus-syslog
There is no extension for syslog. Please raise an issue. Thanks Il dom 5 gen 2020, 17:32 Imran Raza Khan ha scritto: > I want to use camel-quarkus-syslog but its not available or i am using > wrong artifcatid? > > > org.apache.camel.quarkus > camel-quarkus-syslog > >
Hoe to get camel-quarkus-syslog
I want to use camel-quarkus-syslog but its not available or i am using wrong artifcatid? org.apache.camel.quarkus camel-quarkus-syslog
Re: syslog dateformat + log4j syslog appender
The syslog date format in log4j 2 is "MMM dd HH:mm:ss" (SimpleDateFormat
style).
On 7 October 2016 at 04:09, fabryprog <fabrizio.spat...@bizmate.it> wrote:
> Hello everyone,
>
> I'm trying to figure out how to set log4j conversionPattern to be
> compatible
> with the SyslogDateFormat.
>
> I try without results:
>
> log4j.appender.syslog.layout.conversionPattern=%d{ABSOLUTE} %-5p [%c{1}]
> %m
>
> log4j.appender.syslog.layout.conversionPattern=%d{ISO8601} %-5p [%t] %c{2}
> %x - %m%n
>
> Can you help me?
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/syslog-dateformat-log4j-syslog-appender-tp5788476.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
Matt Sicker <boa...@gmail.com>
syslog dateformat + log4j syslog appender
Hello everyone,
I'm trying to figure out how to set log4j conversionPattern to be compatible
with the SyslogDateFormat.
I try without results:
log4j.appender.syslog.layout.conversionPattern=%d{ABSOLUTE} %-5p [%c{1}] %m
log4j.appender.syslog.layout.conversionPattern=%d{ISO8601} %-5p [%t] %c{2}
%x - %m%n
Can you help me?
--
View this message in context:
http://camel.465427.n5.nabble.com/syslog-dateformat-log4j-syslog-appender-tp5788476.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Syslog data format incorrect parsing of structured data
I just create a JIRA[1] and the patch is on the way.
[1]https://issues.apache.org/jira/browse/CAMEL-8687
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On April 22, 2015 at 5:57:38 AM, Sameer Babu K K (sameer...@yahoo.com.invalid)
wrote:
According to RFC 5424 syslog structured data can be like the below examples:
All examples in this section show only the structured data part of
the message. Examples should be considered to be on one line. They
are wrapped on multiple lines in this document for readability
purposes. A description is given after each example.
Example 1 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011]
This example is a structured data element with a non-IANA controlled
SD-ID of type exampleSDID@32473, which has three parameters.
Example 2 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011][examplePriority@32473 class=high]
But the syslog data format
(org.apache.camel.component.syslog.SyslogConverter)
just considers the value till next space as the structured message.
StringBuilder msgId = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
msgId.append(charFound);
}
rfc5424SyslogMessage.setMsgId(msgId.toString());
StringBuilder structuredData = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
structuredData.append(charFound);
}
rfc5424SyslogMessage.setStructuredData(structuredData.toString());
This seems to be a bug to me. Is there a fix or latest version available for
this parsing?
Best Regards,Sameer
Re: Syslog data format incorrect parsing of structured data
Hi
You are welcome to log a JIRA and work on a patch to fix this
http://camel.apache.org/support
On Tue, Apr 21, 2015 at 11:55 PM, Sameer Babu K K
sameer...@yahoo.com.invalid wrote:
According to RFC 5424 syslog structured data can be like the below examples:
All examples in this section show only the structured data part of
the message. Examples should be considered to be on one line. They
are wrapped on multiple lines in this document for readability
purposes. A description is given after each example.
Example 1 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011]
This example is a structured data element with a non-IANA controlled
SD-ID of type exampleSDID@32473, which has three parameters.
Example 2 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011][examplePriority@32473 class=high]
But the syslog data format
(org.apache.camel.component.syslog.SyslogConverter) just considers the value
till next space as the structured message.
StringBuilder msgId = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
msgId.append(charFound);
}
rfc5424SyslogMessage.setMsgId(msgId.toString());
StringBuilder structuredData = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
structuredData.append(charFound);
}
rfc5424SyslogMessage.setStructuredData(structuredData.toString());
This seems to be a bug to me. Is there a fix or latest version available for
this parsing?
Best Regards,Sameer
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Syslog data format incorrect parsing of structured data
According to RFC 5424 syslog structured data can be like the below examples:
All examples in this section show only the structured data part of
the message. Examples should be considered to be on one line. They
are wrapped on multiple lines in this document for readability
purposes. A description is given after each example.
Example 1 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011]
This example is a structured data element with a non-IANA controlled
SD-ID of type exampleSDID@32473, which has three parameters.
Example 2 - Valid
[exampleSDID@32473 iut=3 eventSource=Application
eventID=1011][examplePriority@32473 class=high]
But the syslog data format (org.apache.camel.component.syslog.SyslogConverter)
just considers the value till next space as the structured message.
StringBuilder msgId = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
msgId.append(charFound);
}
rfc5424SyslogMessage.setMsgId(msgId.toString());
StringBuilder structuredData = new StringBuilder();
while ((charFound = (char) (byteBuffer.get() 0xff)) != ' ') {
structuredData.append(charFound);
}
rfc5424SyslogMessage.setStructuredData(structuredData.toString());
This seems to be a bug to me. Is there a fix or latest version available for
this parsing?
Best Regards,Sameer
Re: Sending to Syslog
Thanks I have added the Jar's things are looking better. The route is running now when I send it a formatted message I get the following error: *Message:* 2Jul 10 12:00:00 192.168.1.1 SyslogGen MESSAGE TEXT ERROR | Failed delivery for (MessageId: ID:FM-WLTP082-56545-1418751719052-7:1:1:1:1 on ExchangeId: ID-FM-WLTP082-56542-1418751718711-0-1). Exhausted after delivery attempt: 1 caught: org.apache.camel.TypeConversionException: Error during type conversion from type: java.lang.String to the required type: org.apache.camel.component.syslog.SyslogMessage with value 2Jul 10 12:00:00 192.168.1.1 SyslogGen MESSAGE TEXT due java.lang.NoSuchMethodError: org.apache.camel.component.syslog.SyslogMessage.setTimestamp(Ljava/util/Calendar;)V Seems like I'm missing something. My Route: ?xml version=1.0 encoding=UTF-8? beans xmlns=http://www.springframework.org/schema/beans; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xmlns:camel=http://camel.apache.org/schema/spring; xsi:schemaLocation= http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd; camel:camelContext id=myCamel xmlns=http://camel.apache.org/schema/spring; camel:dataFormats camel:syslog id=mySyslog/ /camel:dataFormats camel:route camel:from uri=activemq:queue:syslogMessages/ camel:marshal ref=mySyslog/ camel:to uri=mina:udp://localhost:514/ /camel:route /camel:camelContext /beans Thanks Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760775.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
I have it working I guess I was missing some more Jar's. Interesting the 1st message seems to work but the second one times out then works. Error Message: ERROR | Failed delivery for (MessageId: queue_syslogMessages_ID_FM-WLTP082-60537-1418754256058-7_1_1_1_1 on ExchangeId: ID-FM-WLTP082-60535-1418754255614-0-1). Exhausted after delivery attempt: 1 caught: org.apache.camel.ExchangeTimed OutException: The OUT message was not received within: 3 millis. Exchange[JmsMessage[JmsMessageID: ID:FM-WLTP082-60537-1418754256058-7:1:1:1:1]] I'm not sure why this would have an issue both systems are local. Thanks Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760776.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
Hi When you get this kind of error it can indicate mixed versions. Can you make sure the version of the Camel JARs are the same version as the version of Camel that was shipped with ActiveMQ. On Tue, Dec 16, 2014 at 7:28 PM, mtod09 m...@thetods.net wrote: I have it working I guess I was missing some more Jar's. Interesting the 1st message seems to work but the second one times out then works. Error Message: ERROR | Failed delivery for (MessageId: queue_syslogMessages_ID_FM-WLTP082-60537-1418754256058-7_1_1_1_1 on ExchangeId: ID-FM-WLTP082-60535-1418754255614-0-1). Exhausted after delivery attempt: 1 caught: org.apache.camel.ExchangeTimed OutException: The OUT message was not received within: 3 millis. Exchange[JmsMessage[JmsMessageID: ID:FM-WLTP082-60537-1418754256058-7:1:1:1:1]] I'm not sure why this would have an issue both systems are local. Thanks Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760776.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Sending to Syslog
Ok I have the solution now. I added sync=false to the uri camel:to uri=mina:udp://localhost:514?sync=false/ It was using request / reply model and waiting for a response. Thanks for all the help. Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760780.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
Hi You need to add JARs to the lib/camel directory of ActiveMQ camel-syslog camel-netty 3.9.4 commons-pool 1.6 camel-mina mina 1.1.7 On Fri, Dec 12, 2014 at 4:33 PM, mtod09 m...@thetods.net wrote: I think I'm seeing a pattern. I thought I could do this using just Spring XML and no code. I'm not a Java programmer so I was hoping to use Spring XML to do all this work. Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760636.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: Sending to Syslog
I think I'm seeing a pattern. I thought I could do this using just Spring XML and no code. I'm not a Java programmer so I was hoping to use Spring XML to do all this work. Thanks -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760636.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
Thanks for the response. I get errors when I try using the dataFormats element. dataFormats syslog id=mySyslog/ /dataFormats Error: because of Data format 'syslog' could not be created Seems like there is a Jar missing but I saw no reference to it in the documentation. Is there a specific JAR required? I'm on ActiveMQ 5.10 not sure what version of Camel that uses. Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760596.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
Hi Mike 2.14.0 camel-activemq is using the 5.10 ActiveMQ client. The doc you linked to earlier shows the dependency on camel-syslog, with maven you just include camel-syslog as a dependency and the data format is defined in there, along with it's dependencies. If you're not using maven, you need to check which dependencies to include. Try the archetype[1] to generate the ActiveMQ project and then add the camel-syslog dependency to the pom as well, and replace the sample camel context with your own and it should work. [1] http://camel.apache.org/camel-maven-archetypes.html Taariq On Thu, Dec 11, 2014 at 9:02 PM, mtod09 m...@thetods.net wrote: Thanks for the response. I get errors when I try using the dataFormats element. dataFormats syslog id=mySyslog/ /dataFormats Error: because of Data format 'syslog' could not be created Seems like there is a Jar missing but I saw no reference to it in the documentation. Is there a specific JAR required? I'm on ActiveMQ 5.10 not sure what version of Camel that uses. Mike -- View this message in context: http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517p5760596.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
On 12/12/14 06:57, Taariq Levack wrote: Hi Mike 2.14.0 camel-activemq is using the 5.10 ActiveMQ client. The doc you linked to earlier shows the dependency on camel-syslog, with maven you just include camel-syslog as a dependency and the data format is defined in there, along with it's dependencies. If you're not using maven, you need to check which dependencies to include. Try the archetype[1] to generate the ActiveMQ project and then add the camel-syslog dependency to the pom as well, and replace the sample camel context with your own and it should work. I recently sponsored the LogAnalyzer package in Debian/Ubuntu and I personally use it with a MongoDB backend. If you are feeding your Camel Syslog data into a similar platform for analysis I'd be interested in any feedback you have. I wrote a brief blog about how to make it work just using the packages: http://danielpocock.com/loganalyzer-rsyslog-mongodb-wheezy-backports
Sending to Syslog
I would like to setup a ActiveMQ queue for syslog messages and use Camel to
send to the Syslog Server.
I looked at the following link but I'm unable to get this to work.
http://camel.apache.org/syslog.html
I'm using Spring for the configuration.
beans
xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd;
bean
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=locations
valuefile:${activemq.conf}/credentials.properties/value
/property
/bean
bean id=myDeadLetterErrorHandler
class=org.apache.camel.builder.DeadLetterChannelBuilder
property name=deadLetterUri value=jms:queue:dead/
property name=redeliveryPolicy
ref=myRedeliveryPolicyConfig/
/bean
bean id=myRedeliveryPolicyConfig
class=org.apache.camel.processor.RedeliveryPolicy
property name=maximumRedeliveries value=3/
property name=redeliveryDelay value=5000/
/bean
camelContext id=Syslog trace=true streamCache=true
xmlns=http://camel.apache.org/schema/spring;
xmlns:km=http://xsdrepo.foundationmedicine.com/messaging/esb;
dataFormats
syslog id=mySyslog/
/dataFormats
route
from uri=activemq:queue:syslogMessages/
marshal ref=mySyslog/
to uri=mina:udp://appdev002.corp.local:10514/
/route
/camelContext
/beans
I keep getting an error loading the datatype.
because of Data format 'syslog' could not be created
Any help would be appreciated.
Mike
--
View this message in context:
http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Sending to Syslog
Hi
Isn't there more details about why syslog cannot be created? Also do
you have the JARs on the classpath for it? And what version of Camel
do you use?
On Wed, Dec 10, 2014 at 7:16 PM, mtod09 m...@thetods.net wrote:
I would like to setup a ActiveMQ queue for syslog messages and use Camel to
send to the Syslog Server.
I looked at the following link but I'm unable to get this to work.
http://camel.apache.org/syslog.html
I'm using Spring for the configuration.
beans
xmlns=http://www.springframework.org/schema/beans;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd;
bean
class=org.springframework.beans.factory.config.PropertyPlaceholderConfigurer
property name=locations
valuefile:${activemq.conf}/credentials.properties/value
/property
/bean
bean id=myDeadLetterErrorHandler
class=org.apache.camel.builder.DeadLetterChannelBuilder
property name=deadLetterUri value=jms:queue:dead/
property name=redeliveryPolicy
ref=myRedeliveryPolicyConfig/
/bean
bean id=myRedeliveryPolicyConfig
class=org.apache.camel.processor.RedeliveryPolicy
property name=maximumRedeliveries value=3/
property name=redeliveryDelay value=5000/
/bean
camelContext id=Syslog trace=true streamCache=true
xmlns=http://camel.apache.org/schema/spring;
xmlns:km=http://xsdrepo.foundationmedicine.com/messaging/esb;
dataFormats
syslog id=mySyslog/
/dataFormats
route
from uri=activemq:queue:syslogMessages/
marshal ref=mySyslog/
to uri=mina:udp://appdev002.corp.local:10514/
/route
/camelContext
/beans
I keep getting an error loading the datatype.
because of Data format 'syslog' could not be created
Any help would be appreciated.
Mike
--
View this message in context:
http://camel.465427.n5.nabble.com/Sending-to-Syslog-tp5760517.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Unable to consume syslog messages
sscott wrote I set up rsyslogd to forward *.* to localhost:5140. Every log message causes Camel to output an InvalidPayloadException caused by a NoTypeConversionAvailableException with the detail No type converter available to convert from type: org.jboss.netty.buffer.BigEndianHeapChannelBuffer to the required type: java.io.InputStream with value BigEndianHeapChannelBuffer(ridx=0, widx=105, cap=105) When I change the from() to be mina:, with or without the sync=false and allowDefaultCodec=false options, and change the maven dependencies to camel-mina from camel-netty, the same exceptions are thrown with the detail No body available of type: java.io.InputStream on: Message: [Body is null]. Caused by: No type converter available to convert from type: null to the required type: java.io.InputStream with value null. In case anybody ever has this problem in the future, it was caused by using maven-assembly-plugin to package all the code into a jar-with-dependencies. I'm assuming it's a TypeConverter / MANIFEST.MF issue. -- View this message in context: http://camel.465427.n5.nabble.com/Unable-to-consume-syslog-messages-tp5724850p5725140.html Sent from the Camel - Users mailing list archive at Nabble.com.
Unable to consume syslog messages
I'm attempting to use camel-syslog as detailed at
http://camel.apache.org/syslog.html to consume syslog messages. I'm using
Camel 2.10.2, Oracle JDK 1.6.0_31 64-Bit on CentOS 6.2.
I set up a simple test using Netty:
val ctx = new DefaultCamelContext
val dataFormat = new Rfc3164SyslogDataFormat
ctx.addRoutes(new RouteBuilder() {
def configure() {
from(netty:udp://localhost:5140?sync=falseallowDefaultCodec=false)
.setExchangePattern(ExchangePattern.InOnly)
.unmarshal(dataFormat)
.bean(classOf[SyslogBean])
}
})
ctx.start()
(SyslogBean has a single method that accepts a
o.a.c.component.syslog.SyslogMessage and logs it).
I set up rsyslogd to forward *.* to localhost:5140. Every log message
causes Camel to output an InvalidPayloadException caused by a
NoTypeConversionAvailableException with the detail No type converter
available to convert from type:
org.jboss.netty.buffer.BigEndianHeapChannelBuffer to the required type:
java.io.InputStream with value BigEndianHeapChannelBuffer(ridx=0, widx=105,
cap=105)
When I change the from() to be mina:, with or without the sync=false and
allowDefaultCodec=false options, and change the maven dependencies to
camel-mina from camel-netty, the same exceptions are thrown with the detail
No body available of type: java.io.InputStream on: Message: [Body is null].
Caused by: No type converter available to convert from type: null to the
required type: java.io.InputStream with value null.
This probably is more of a netty/mina question than a syslog dataformat
question, any help is appreciated
--
View this message in context:
http://camel.465427.n5.nabble.com/Unable-to-consume-syslog-messages-tp5724850.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Writing to local syslog with camel
Problem with this solution is that SyslogAppender limits packet to 1024bytes. Additionally I do not like the idea, that part of the camel configuration is kept in *log4j.configuration (appender, format), but this argument is very personal :D -- View this message in context: http://camel.465427.n5.nabble.com/Writing-to-local-syslog-with-camel-tp5558225p5560396.html Sent from the Camel - Users mailing list archive at Nabble.com.
Writing to local syslog with camel
Hi I'm looking for easiest way to redirect message to the local syslog using camel. (sth like .to(syslog:args)) Here is what I've found so far: * use camel-syslog component - usefull when you need to consume syslog message or integrate with mina or netty component, but not very helpfull in this case * use camel-exec component - used to execute system commands so should work; did not test it yet * use camel-mina or camel-netty component - that would require syslog's reconfiguration, so that it will listen on some udp port; prefer not to do it this way * write new component - that's finality Thanks for any tips Lukas -- View this message in context: http://camel.465427.n5.nabble.com/Writing-to-local-syslog-with-camel-tp5558225p5558225.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Writing to local syslog with camel
On Mon, Mar 12, 2012 at 9:56 AM, karpaczio karpac...@gmail.com wrote: I'm looking for easiest way to redirect message to the local syslog using camel. (sth like .to(syslog:args)) Here is what I've found so far: Both slf and log4j have syslog appenders. I'd use one of those. Larry
Re: Writing to local syslog with camel
On Mon, Mar 12, 2012 at 5:07 PM, Larry Meadors larry.mead...@gmail.com wrote: On Mon, Mar 12, 2012 at 9:56 AM, karpaczio karpac...@gmail.com wrote: I'm looking for easiest way to redirect message to the local syslog using camel. (sth like .to(syslog:args)) Here is what I've found so far: Both slf and log4j have syslog appenders. I'd use one of those. Yeah that is a proven solution. That said, we love contributions to Apache Camel. So if anyone steps up and create a syslog appender for camel-syslog, then that would be cool too. Larry -- Claus Ibsen - FuseSource Email: cib...@fusesource.com Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
Re: Netty with syslog decoder
Hi Claus Ibsen, Thank you for responding on this, I have already gone thru camel-syslog component, it just provides a DataFormat to convert BSDSyslog stream into string, but it doesn't have any codec implementation to collect all the data over TCP. I am looking for help in how to create my own codec for Netty. Thanks, Trivedi -- View this message in context: http://camel.465427.n5.nabble.com/Netty-with-syslog-decoder-tp4763467p4765477.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Netty with syslog decoder
There is a camel-syslog component. Maybe there is some pieces in there
you can use?
On Fri, Sep 2, 2011 at 8:57 PM, trivedikumarb trivedikuma...@gmail.com wrote:
Hi All,
I am trying to expose TCP endpoint using Netty
[from('netty:tcp://localhost:12346?sync=falseallowDefaultCodec=falseencoding=UTF-8disconnect=true')],
from the client I am sending a big syslog message. At the server side, I am
receiving the message as chunks instead of full byte[] or string. Can
someone help me or guide me on how to write decoder to handle this?
Thanks,
Trivedi
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-with-syslog-decoder-tp4763467p4763467.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
FuseSource
Email: cib...@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.blogspot.com/
Author of Camel in Action: http://www.manning.com/ibsen/
Netty with syslog decoder
Hi All,
I am trying to expose TCP endpoint using Netty
[from('netty:tcp://localhost:12346?sync=falseallowDefaultCodec=falseencoding=UTF-8disconnect=true')],
from the client I am sending a big syslog message. At the server side, I am
receiving the message as chunks instead of full byte[] or string. Can
someone help me or guide me on how to write decoder to handle this?
Thanks,
Trivedi
--
View this message in context:
http://camel.465427.n5.nabble.com/Netty-with-syslog-decoder-tp4763467p4763467.html
Sent from the Camel - Users mailing list archive at Nabble.com.
