Skip to content
Support for Log4j2 using the IOpipe Logger Plugin.
Branch: master
Clone or download
adjohn Merge pull request #3 from adjohn/adjohn-docs-1
Add instructions for setting the Lambda env var
Latest commit 89019de Mar 26, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.circleci Do not publish sources and JavaDoc into layers. Feb 25, 2019
src Reporting of log4j2 logs to IOpipe. Oct 10, 2018
.gitignore Initial commit Sep 28, 2018
.version-rules.xml Correct filename. Feb 25, 2019
LICENSE Initial commit Sep 28, 2018
README.md Add instructions for setting the Lambda env var Mar 25, 2019
pom.xml Set version to 1.2.0. Feb 25, 2019

README.md

IOpipe Logger Adapter for log4j2 (Java)

Download CircleCIJavadocs

Support for Log4j2 using the IOpipe Logger Plugin. This plugin is to be used with the IOpipe Java Agent.

It is licensed under the Apache 2.0.

Building With The Adapter

Your pom.xml file may be modified to include the following dependency:

<dependency>
  <groupId>com.iopipe</groupId>
  <artifactId>iopipe-logger-log4j2</artifactId>
</dependency>

Due to the way shading works, you will be required to always use the Log4j2 Transformer if you wish to support multiple appenders within your project and its dependencies. Not doing so may result in not being able to use multiple various plugins with Log4j2.

Configuration

Configuring your project to use this adapter for Log4j2 will be the same as configuring other appenders as specified in the configuration documentation.

Using the following as an example log4j2.xml resource at a very basic level to report to IOpipe (the error level may be modified accordingly as needed):

<?xml version="1.0" encoding="UTF-8"?>
<Configuration status="error">
  <Appenders>
    <IOpipe name="IOpipe">
    </IOpipe>
  </Appenders>
  <Loggers>
    <Root level="error">
      <AppenderRef ref="IOpipe" />
    </Root>
  </Loggers>
</Configuration>

Once you’re setup, you will need to configure IOpipe to enable the logging plugin. You can do this by setting the IOPIPE_LOGGER_ENABLED environment variable to true in the AWS Lambda configuration.

You can’t perform that action at this time.