Prerequisites for the Pickup LogEvents Service Logging Agent

Get ready for a seamless, high-performance logging experience with the Nodinite Pickup LogEvents Service Logging Agent. This page provides everything you need to prepare your environment for secure, reliable, and scalable integration—whether on-premises or in the cloud.

On this page, you will learn how to:

• ✅ Ensure your environment meets all software and platform requirements
• ✅ Configure user rights and firewall settings for secure operation
• ✅ Optimize for high-performance, on-premises or cloud deployments
• ✅ Apply best practices for integrating with message brokers, databases, and file systems

This page details the prerequisites for successfully installing and running the Nodinite Pickup Log Events Service Logging Agent.

The diagram above illustrates the supported logging options and how the Pickup LogEvents Service Logging Agent integrates With Nodinite, message brokers, file systems, and databases.

You can install this agent on-premises using TCP/IP for local network access or in the cloud/off-site using Service Bus Relaying. As long as the Log API is accessible on the configured port, you can deploy flexibly. For high-performance installations, install the agent close to the database (ideally on the same network as Nodinite).

We recommend installing this agent near the Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite server).

Software Requirements

Versions 7.0.4 and later require .NET 10 Hosting Bundle.

Platform Requirements

Message Queue Systems

Azure Services

Database Systems

Versions 6.0 and later require .NET Framework 4.8 or later.
Versions 5.4 and later require .NET Framework 4.6.2 or later.
Versions before 5.4 require .NET Framework 4.5.2 or later.

Source System User Rights

The Pickup Service requires specific permissions on each source system. Configure credentials and permissions according to your source type:

Message Queue Systems

ActiveMQ - Basic authentication with Admin rights (ActiveMQ security)

AMQP - Basic authentication with Admin rights

Anypoint MQ - Basic auth or Connected Apps with Admin rights (AnypointMQ security)

MSMQ - Integrated Windows security: Peek, Read, Delete permissions

Azure Cloud Services

Azure Service Bus - SAS token connection string with Manage + Listen claims

Azure Event Hub - SAS token connection string with Manage + Listen claims; Storage account requires Blob Data Reader/Contributor role

Azure Blob Storage - Storage account connection string with appropriate access permissions

File Systems

File Shares - Integrated Windows security: Read, Write, Delete permissions on SMB shares

Database Systems

PostgreSQL - Database user with SELECT, INSERT, UPDATE, DELETE on log event tables

SQL Server - Database user with:

• public - logon rights
• db_datareader - read access
• db_datawriter - write access
• db_ddladmin - better performance (optional)

Tip

For connection string examples and authentication options, see the comprehensive SQL Connection Strings guide.

For detailed configuration including connection strings and authentication examples, see the specific Configuration guides for each source type.

Supported Versions

Cloud technologies evolve rapidly. Nodinite always supports currently supported Microsoft API versions. Update Nodinite and the Pickup Log Events Service Logging Agent as needed.

What Windows User Rights does the Pickup LogEvents Service Logging Agent require?

The agent is installed as a Windows Service, usually on the Nodinite application server. Virtual machines are supported.

Service Account Options ^{New 7.0.4}

Group Managed Service Account (gMSA) - Recommended for automated password management.

• No password expiration or manual rotation
• Enhanced security with automatic 240-character passwords
• Simplified management across multiple servers
• See Configure Group Managed Service Accounts (gMSA) for setup instructions

Traditional Account - Local named account or domain account (preferred).

• Requires manual password management
• Follow the 'How to set logon as a Windows service right' user guide for detailed instructions

What Nodinite SQL user rights does the Pickup LogEvents Service Logging Agent require?

If you are bypassing the Log API for performance reasons (the only valid reason), then the account running the Pickup Log Events Service Logging Agent must have the following rights assigned:

Important

db_ddladmin is required for the service account to have proper rights to read statistics. Without this permission, performance may be degraded, especially for remote servers (linked servers). Read more in Microsoft's documentation.

Configuration Database Permissions

The Configuration Database requires:

• db_datareader
• db_datawriter
• db_ddladmin
• Execute rights on all existing and future stored procedures:

GRANT EXECUTE TO [Domain\user]

Replace [Domain\user] with the Windows account used for the Pickup Log Events Service Logging Agent.

Tip

For detailed connection string configuration including Windows Authentication, SQL Authentication, and encryption settings, see SQL Connection Strings.

Log Database Permissions

All Log Databases (can be multiple) require:

• db_datareader
• db_datawriter
• db_ddladmin

Firewall Requirements

The Pickup Service requires network connectivity between multiple systems. Below are the essential firewall rules organized by source type.

Note

Stateful Firewall Note: Modern firewalls automatically allow response traffic for established outbound connections. Inbound rules shown below typically require no additional configuration with stateful firewalls.

Firewall Rules by Source Type

Required Connections to Nodinite

Performance Tip: When the Pickup Service and Log API are on the same server, use HTTP (port 80) for better performance.

Additional Firewall Considerations

Azure Storage Firewall: When using Event Hub or Azure Storage, you may need to whitelist the Pickup Server's public IP. Review Configure Azure Storage firewalls.

DNS Resolution: All connections require DNS (TCP/UDP port 53) or static hosts file entries.

EnableLinkRedirect: If enabled for Event Hub (default), additional dynamic ports (104XX range) may be used. Review AMQP 1.0 protocol guide.

RPC Dynamic Ports: For SQL Server named instances and MSMQ, RPC uses dynamic port allocation. Review Configure RPC dynamic port allocation.

Tip

For detailed protocol documentation and troubleshooting, see:

• SQL Server Firewall Configuration
• SMB File Sharing Ports
• MSMQ Ports
• Azure Event Hubs Troubleshooting

Frequently Asked Questions

Find additional solutions to common problems and the FAQ for the Nodinite Pickup Log Events Service Logging Agent in the Troubleshooting user guide.

Make sure to subscribe to our Release Notes.

Next Step

• Install the Pickup LogEvents Service Logging Agent

Related Topics

• Administration