此内容没有您所选择的语言版本。
Chapter 205. Lumberjack Component
Available as of Camel version 2.18
The Lumberjack component retrieves logs sent over the network using the Lumberjack protocol, from Filebeat for instance. The network communication can be secured with SSL.
This component only supports consumer endpoints.
Maven users will need to add the following dependency to their pom.xml for this component:
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-lumberjack</artifactId>
<version>x.x.x</version>
<!-- use the same version as your Camel core version -->
</dependency>205.1. URI format
lumberjack:host lumberjack:host:port
You can append query options to the URI in the following format, ?option=value&option=value&…
205.2. Options
The Lumberjack component supports 3 options which are listed below.
| Name | Description | Default | Type |
|---|---|---|---|
| sslContextParameters (security) | Sets the default SSL configuration to use for all the endpoints. You can also configure it directly at the endpoint level. | SSLContextParameters | |
| useGlobalSslContext Parameters (security) | Enable usage of global SSL context parameters. | false | boolean |
| resolveProperty Placeholders (advanced) | Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. | true | boolean |
The Lumberjack endpoint is configured using URI syntax:
lumberjack:host:port
with the following path and query parameters:
205.2.1. Path Parameters (2 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| host | Required Network interface on which to listen for Lumberjack | String | |
| port | Network port on which to listen for Lumberjack | 5044 | int |
205.2.2. Query Parameters (5 parameters):
| Name | Description | Default | Type |
|---|---|---|---|
| bridgeErrorHandler (consumer) | Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. | false | boolean |
| sslContextParameters (consumer) | SSL configuration | SSLContextParameters | |
| exceptionHandler (consumer) | To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this options is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. | ExceptionHandler | |
| exchangePattern (consumer) | Sets the exchange pattern when the consumer creates an exchange. | ExchangePattern | |
| synchronous (advanced) | Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). | false | boolean |
205.3. Result
The result body is a Map<String, Object> object.
205.4. Lumberjack Usage Samples
205.4.1. Example 1: Streaming the log messages
RouteBuilder builder = new RouteBuilder() {
public void configure() {
from("lumberjack:0.0.0.0"). // Listen on all network interfaces using the default port
setBody(simple("${body[message]}")). // Select only the log message
to("stream:out"); // Write it into the output stream
}
};