This directory contains several examples that show how the appenders are configured. Each has its own README file that goes into further detail on its operation.
-
Writes logging messages to each of the destinations using Log4J 1.x and the version 1 AWS SDK.
-
A web-app that demonstrates how to initialize and shut down Log4J 1.x using a
ContextListener
, along with adding a unique request token to the mapped diagnostic context to track each request's progress. This example uses the version 1 AWS SDK. -
Writes logging messages to each of the destinations using Log4J 2.x and the AWS version 2 SDK.
-
A web-app that uses Log4J 2.x. This example relies on Log4J's integration with Servlet 3.0 for configuration and shutdown, rather than using an explicit
ContextListener
. Like the other webapp examples, it includes a servlet filter that adds a unique request token to the mapped diagnostic context to track each request's progress. This example uses the version 2 AWS SDK. -
Writes logging messages to each of the destinations using Logback and the AWS version 1 SDK. The POM for this example demonstrates using an exclusion to avoid loading the
commons-logging
framework, which is a transitive dependency of the SDK. -
A web-app that demonstrates how to initialize and shut down Logback with a
ContextListener
, along with adding a unique request token to the mapped diagnostic context to track each request's progress. This example uses the version 1 AWS SDK.
In addition, there are CloudFormation templates to create the destinations used by these examples, along with templates for an Elasticsearch cluster and Kinesis Firehose to create a complete logging pipeline.