- 6 minutes to read

Release Notes

Nodinite Pickup LogEvents Service Logging Agent

Experience true end-to-end tracking and integration with the Nodinite Pickup LogEvents Service Logging Agent. This page explains how you can fetch log events from virtually any message broker, file system, or cloud service, and highlights the unique selling points that make this agent a must-have for modern integration landscapes.

✅ Achieve seamless end-to-end tracking across all platforms
✅ Reduce custom code and simplify integration
✅ Benefit from AI-powered diagnostics and secure secret management
✅ Effortlessly support a wide range of sources and protocols

New 7.x The latest version comes with brand new features:

Info

Use the Nodinite Pickup LogEvents Service Logging Agent to achieve true end-to-end tracking by asynchronously fetching custom-coded Nodinite Log Events.

The Nodinite Pickup LogEvents Service Logging Agent empowers your integration landscape by reliably fetching your custom-coded Nodinite Log Events from a wide range of sources—including message brokers, file systems, and cloud storage. This approach reduces the amount of custom code you need to maintain and ensures robust, reliable logging for your solutions.

The Nodinite Pickup LogEvents Service Logging Agent empowers your integration landscape by reliably fetching your custom-coded Nodinite Log Events from a wide range of sources—including message brokers, file systems, and cloud storage. This approach reduces the amount of custom code you need to maintain and ensures robust, reliable logging for your solutions.

How the Pickup LogEvents Service Logging Agent Works

Below is a visual example of how the Pickup LogEvents Service Logging Agent bridges your integration solutions and the Nodinite platform, enabling seamless, asynchronous log event collection from various sources.

graph LR subgraph "Systems Integration Solutions" roStrategy(fal:fa-lightbulb-on Logging Strategy) --> roBroker{fal:fa-brackets-curly Reusable
Generic Logging logic} roBroker --> |Nodinite JSON Log Event|roSink(fal:fa-file-export Intermediate storage ) roBroker -.-> |"Other format(s)"| ro2["Other Log destination(s)"] end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) -->roNI(fal:fa-cloud-arrow-down Log API) roSink --> roPS end

The diagram above illustrates how the Nodinite Pickup LogEvents Service Logging Agent collects log events from your integration solutions and delivers them to the Nodinite platform for monitoring, analytics, and compliance.

When your message broker or solution lacks built-in tracking, simply produce a JSON-formatted log event and place it on a highly available intermediate storage. The Pickup LogEvents Service Logging Agent will handle the rest, ensuring your logs reach Nodinite for monitoring, analytics, and compliance.

Some real-world examples include:

Unlike traditional Logging Agents, the Pickup LogEvents Service Logging Agent reads Nodinite Log Events from sources like disks or queues and forwards them to the Nodinite Log API (RESTful). For high-performance, on-premises solutions, you can even bypass the Log API and write directly to the Log Database.

Features

Source Description Recommended Monitoring Agent External Link Configuration
ActiveMQ Fetch Log Events from ActiveMQ/ActiveMQ Artemis queues Message Queuing Agent Apache NMS ActiveMQ Configuration
AMQP New 6.2 Fetch Log Events from AMQP v1.0/ActiveMQ Artemis queues Message Queuing Agent AMQP.org Configuration
AnypointMQ Fetch Log Events from MuleSoft Cloudhub AnypointMQ platform Message Queuing Agent AnypointMQ Configuration
Azure Event Hub Fetch Log Events from EventHub; Create the Log Event using the Nodinite Serilog EventHub sink Azure Monitoring Agent EventHub Configuration
Azure ServiceBus Fetch Log Events from Azure Service Bus; Create the Log Event using the Nodinite Serilog ServiceBus sink Message Queuing Agent Azure Service Bus Configuration
Azure Blob New 6.2 Fetch Log Events from Azure Storage Account Azure Monitoring Agent Azure Blob Storage Configuration
Disk / Folder Fetch Log Events from file folders and SMB enabled shares; Create the Log Event using the Nodinite Serilog File sink File Monitoring Agent Configuration
Microsoft MSMQ
NOTE: DEPRECATED - This feauture is no longer available with 7.1.x and later		 Fetch Log Events from Microsoft MSMQ Message Queuing Agent Configuration
Microsoft SQL Server Fetch Log Events from Microsoft SQL Server Database Monitoring Agent Configuration
PostgreSQL Fetch Log Events from PostgreSQL database instances Database Monitoring Agent PostgreSQL Configuration

Tip

Missing a source? Contact our support at support@nodinite.com

The agent performs logging by sending an HTTP/HTTPS POST of a Log Event to the api/LogEvent/LogEvent endpoint. For high-performance, on-premises solutions, you can bypass the Log API and write Log Events directly to the proper Log Database using multiple threads.

Frequently Asked Questions

Find more solutions and answers in the Troubleshooting user guide.

Why You Should Not Send Log Events Directly to the Log API

⚠️ Direct logging might seem simple — but it's often a risky shortcut.
The real power lies in reliable, asynchronous logging.

The Problem with Direct Log API Calls

Sending Log Events directly to the Nodinite Log API may work under ideal conditions. But in real-world systems, things rarely stay perfect.

Your solution must handle every possible failure in real time — otherwise, critical logs may be lost, delayed, or never captured at all.

Here are just a few scenarios that could cause problems:

  • 🔌 Network interruptions (temporary loss of connectivity)
  • 💻 Windows Server reboots or maintenance (planned or unplanned)
  • 🔄 Nodinite service restarts or updates
  • 🧱 Database outages or full disk storage
  • 🔐 Security changes (firewalls, certificates, identity)
  • 📉 High load or performance bottlenecks
  • ⛔ Log API throttling or timeouts

These scenarios require error handling, retry logic, and buffering — all of which make your integration more complex and harder to maintain.

The Better Way: Use the Pickup LogEvents Service

The Nodinite Pickup LogEvents Service (a Logging Agent) solves these challenges for you.

Instead of pushing events directly to the Log API, your system writes log events to a local queue or file. The Pickup Agent then processes and sends them to Nodinite asynchronously — with built-in retry, throttling, and fault tolerance.

✅ Benefits of Using the Pickup Logging Agent:

Benefit What It Means for You
Decoupled architecture Your solution doesn't depend on Nodinite being online
Built-in reliability Resilient to network or service outages
Automatic retry Events are not lost if delivery fails temporarily
Queue-based pacing Avoids overloading Nodinite or the Log API during high traffic
Faster processing Your main process doesn’t wait for API acknowledgments
Simplified error handling Centralized logging agent handles failures, not your business logic
Easier monitoring & maintenance You can monitor the agent's status independently of your application
graph LR A[Your App] -->|Direct POST| API[Nodinite Log API] subgraph Risky Path API -.->|Fails if API is down| X[Log lost or delayed] end

The diagram above shows the risky path: direct logging to the Log API can result in lost or delayed logs if the API is unavailable.

graph LR A[Your App] -->|"Write Log Event"| Q["Intermediate Storage (Queue/File)"] Q -->|Pickup Agent| API[Nodinite Log API] subgraph Reliable Path Q -.->|Buffering, Retry| API end

The diagram above shows the recommended path: your app writes log events to intermediate storage, and the Pickup Agent reliably delivers them to Nodinite, even if the Log API is temporarily unavailable.

Next Step

Configuring the Nodinite Pickup Log Events Logging Service
Install Nodinite Pickup Log Events Loggng Service
Prerequisites
Updating the Nodinite Pickup Log Events Logging Service

Add or manage Log Agents
Add or manage Log View
Log Agents
Log Views