- 4 minutes to read

Release Notes

Nodinite Pickup LogEvents Service Logging Agent

Info

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

The Nodinite Pickup LogEvents Service Logging Agent asynchronously fetches your custom-coded Nodinite Log Events from many different sources (e.g. intermediate storage), which means you will get less code and reliable logging in your custom-built solutions.

Nodinite Pickup LogEvents Service Logging Agent

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 -.-> |"The other format(s)"| ro2["Other Log destination(s)"] end subgraph "Nodinite instance" roPS(fal:fa-truck-pickup Pickup Service) -->roNI(fal:fa-cloud-download Log API) roSink --> roPS end

When built-in tracking does not exist in your message broker/solution, your mission is to produce a JSON-formatted log event and place it on a highly available intermediate storage (source).

Some real-world examples are below:

The Nodinite Pickup LogEvents Service Logging Agent is not a Logging Agent with logic like other Logging Agents; it reads Nodinite Log Events from a source like a disk or a queue and then sends them to the Nodinite Log API (RESTful).

  • IBM Sterling - custom code
  • IBM Cloud - custom code, for example, to a PostgreSQL database instance(s)
  • Java-based solutions
  • Azure functions - using Serilog The pickup Service fetches Log Events from the following sources:

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 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

Info

Missing a source? Please get in touch with our support,support@nodinite.com, and we will build it for you.

The logging is internally then performed using an HTTP/HTTPS POST of a Log Event to the api/LogEvent/LogEvent endpoint. For high-performance solutions on-premise, there is also an option to bypass the Log API and write the Log Events using many threads directly to the active online Log Database.

Frequently asked questions

Additional solutions to common problems and the Nodinite Pickup LogEvents Service Logging Agent FAQ exist in the Troubleshooting user guide.

Why should I NOT send my Log Events directly to the LogAPI?

That would mean that your solution would have to deal with error handling to cope with occasions when Nodinite for various reasons is unavailable like:

  • Network errors
  • Windows Servers are not available pending/during a reboot (Restart/maintenance window/security patches)
  • During updates of Nodinite
  • Database disks that run out of disk space, typically used for the Nodinite Log Databases
  • Security changes where services no longer work (due to accidental or changes by mistake)
  • ...

Also, from an overload perspective, there is less stress on the Nodinite instance since the fetch process performs at a controlled pace when we are online, available, and healthy.

Read more about the differences between Synchronous and Asynchronous messaging in this Wikipedia article.

Next Step

Prerequisites
Install Nodinite Pickup Service
Configuring the Nodinite Pickup Service
Update

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