- 2 minutes to read

How to enable Logging from Apache Camel solutions to Nodinite

Learn how to perform Asynchronous Logging from Apache Camel to Nodinite. Some custom coding is required.

You must add custom logging code to your Apache Camel solution in order to enable logging of business transactions to Nodinite

graph LR subgraph "Apache Camel" roBroker(fal:fa-brackets-curly Custom Code)-->roSink(fal:fa-file-export Intermediate storage ) end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) -->roNI(fal:fa-cloud-download Log API) roSink --> roPS end

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 Apache Camel solution. You do now want to hard code this in order to separate logged events from many types of environments (e.g. Prod, Test, QA, ...)

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.

Your intermediate storage should be local and highly available

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

4. Move logged events using the Nodinite Pickup Service

The pickup Service fetches Log Events from the following sources:

Source Description Recommended Monitoring Agent External Link Configuration
Disk / Folder Fetch Log Events from file folders and SMB enabled shares File Monitoring Agent Configuration
ActiveMQ Fetch Log Events from ActiveMQ queues Message Queuing Agent Apache NMS ActiveMQ Configuration
MSMQ Fetch Log Events from Microsoft MSMQ Message Queuing Agent Configuration
Azure ServiceBus Fetch Log Events from Azure Service Bus Message Queuing Agent Azure Service Bus Configuration
PostgreSQL Fetch Log Events from PostgreSQL database instances Database Monitoring Agent PostgreSQL Configuration
Event Hub Fetch Log Events from EventHub N/A EventHub Configuration
AnypointMQ Fetch Log Events from Mulesoft Cloudhub AnypointMQ platform Message Queuing Agent AnypointMQ Configuration

Missing a source? please contact our support, support@nodinite.com and we will build it for you

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.