-
Notifications
You must be signed in to change notification settings - Fork 170
Suro log4j appender configuration
metacret edited this page Apr 26, 2013
·
6 revisions
com.netflix.suro.input.Log4jAppender can be used as the Suro client. Let's assume you defined Suro log4j appender as the following:
log4j.appender.SURO=com.netflix.suro.input.Log4jAppender
The common prefix log4j.appender.SURO is omitted at the table.
| Key | Description | Default value |
|---|---|---|
| formatterClass | Log4j appender is converting LoggingEvent object to text data only. formatterClass is implementing logic how to convert LoggingEvent object to text. | JsonLog4jFormatter |
| datetimeFormat | The format of datetime field in log line | yyyy-MM-dd'T'HH:mm:ss,SSS |
| app | Message header application tag | defaultApp |
| dataType | Message header data type tag | defaultDataType |
| routingKey | If formatter class contains logic to extract routing key from LoggingEvent object, message routing key will be set the one from formatter class. Otherwise, the default routing key is needed | defaultRoutingKey |
The following properties are same as the Suro client configurations
- compression
- loadBalancerType
- loadBalancerServer
- clientType
- asyncQueueType
- asyncMemoryQueueCapacity
- asyncFileQueuePath
SerDe is not needed because log4j is always doing SerDe with String.