How to enable Logging from WSO2 Enterprise Integrator solutions to Nodinite

Learn how to perform Asynchronous Logging from WSO2 Enterprise Integrator to Nodinite. Some custom coding is required.

You must add custom logging code to your WSO2 Enterprise Integrator solution in order to enable logging of business transactions to Nodinite

Step by step guide

Follow the steps outlined below.

1. Create the event

In your flows, make sure to add custom logging (regardless of the target). Typically this is done using Log4J or other similar frameworks depending on your design, policy and needs

2. Convert the logged event to Nodinite format

You must translate your logs to Nodinite JSON Log Event.

In order to uniquely identify the Log Agent, you must provide a LogAgentValueId. You should allow the LogAgentValueId (mandatory number) to be configurable part of the WSO2 Enterprise Integrator solution. You do now want to hardcode this in order to separate logged events from many types of environments (e.g. Prod, Test, QA, ...)

Tip

Make sure to get the best out of the information you have. Map existing properties to the standard properties and attach context and payload as needed

3. Send Event to intermediate storage

The Nodinite Pickup Service can fetch the logged events from many intermediate storages.

Important

Your intermediate storage should be local and highly available.

Tip

Do not send your logged events synchronously to the Nodinite Log API. You should honour the asynchronous pattern using the Nodinite asynchronous Pickup Service

4. Move logged events using the Nodinite Pickup Service

The Nodinite Pickup Service fetches Log Events from many intermediate storages. Consume the Log Events from any of these that fit your purpose.

5. Enable self-service from within Nodinite

Now that you have data logged inside Nodinite you can start to create Role based Log Views and invite your business to share insights and data from your logging.