- 2 minutes to read

Asynchronous logging with Nodinite

Enables reliable messaging using asynchronous message logging pattern and avoid dependencies and overloading of any of the systems used for your system integration solutions

Some integration platforms and technologies offer built-in tracking or at least have a way to attach a log appender. This makes it very easy to get logged events and data from the application/flow/solutions to Nodinite. Some good examples are:

However, some platforms require you to add custom code to emit events and data. You should always avoid coding in a way that is vendor-specific (you should only need to change code in 1 place if you replace/enable/disable the logging solution)

Your mission when built-in tracking does not exist in your message broker/solution using any of the Nodinite Logging Agents is to produce a json formatted log event and place it on a highly available target (e.g. a queue, a file share, a database, ...).

The Nodinite Pickup LogEvents Service Logging Agent when available then fetches your LogEvents asynchronously which means you will get less code, reliable logging and avoid overloading Nodinite in your custom-built solutions.

graph LR subgraph "App Server" roLogSink("fal:fa-bolt Custom Logging Solution
.NET/.NET Core
Mule ESB
Java/NodeJS/...") --> roId1["fal:fa-list Queue
fal:fa-folder Folder
..."] end subgraph "Nodinite Server" roLogAPI(fal:fa-cloud-download Log API) roPS(fal:fa-truck-pickup Pickup Service)--> roLogAPI roId1 -. Async.-x roPS end

Next Step