Prerequisites for the Nodinite Log File Parser Monitoring Agent

Unlock seamless, secure, and scalable log file monitoring with the Nodinite Log File Parser Monitoring Agent. On this page, you will:

• ✅ Understand all system and network requirements for a smooth installation
• ✅ Learn how to configure user rights and firewall settings for robust security
• ✅ Discover best practices for deploying the agent on-premise or in the cloud
• ✅ Ensure compliance and minimize troubleshooting with clear, actionable guidance

This page details everything you need to successfully install and run the Nodinite Log File Parser Monitoring Agent.

Architecture: The Log File Parser Monitoring Agent connects securely to multiple SMB shares and folders, enabling end-to-end monitoring of diverse log file formats.

Please use RegEx101 or a similar tool to test your RegEx expressions. You must practice RegEx to use this agent effectively.

You can install instances of this agent on-premise using TCP/IP for local network access, or in the cloud/off-site using Service Bus Relaying.

We recommend that you keep this agent close to the installation of Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)

Software Requirements

Versions 7.0.4 and later require .NET 10 Hosting Bundle.

Versions 7.0.4 and later require .NET 10 Hosting Bundle.
.NET 10 minimum OS: Windows Server 2012 / 2012 R2.
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.

What Windows User Rights does the Log File Parser Monitoring agent require?

You install the agent as a Windows Service, typically on the Nodinite application server. Virtual machines are fully supported.

Service Account Options ^{New 7.0.4}:

• Group Managed Service Account (gMSA) - Recommended for automated password management. See Configure Group Managed Service Accounts (gMSA) for setup instructions.
• Traditional Account - Use a local named account or a domain account (preferred).
  • Follow the 'How to set logon as a Windows service right' user guide for detailed instructions.

Least privileges (basic usage)

• Grant read permission to the folder where you want to check for files (and all its child folders if the 'Include child folders' option is checked)

What Firewall settings are required for the Log File Parser Monitoring agent?

Where you install the Nodinite Log File Parser Monitoring Agent in relation to the Nodinite Monitoring Service and the file shares with your log files determines your firewall configuration. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.

Network diagram: the Monitoring Service calls the agent, and the agent reads the log files on the SMB shares. Dashed arrows are optional hops.

Note

When the agent runs on the Core Services Server (the typical installation), you need no firewall rule between the Monitoring Service and the agent. Log files on local disks of the Agent Server need no firewall rule at all.

Between the Monitoring Service and the Log File Parser Monitoring Agent

The Monitoring Service opens every connection; the agent never calls it. On Windows Server, Nodinite v7 hosts the agent as its own IIS web site, on a port you set per environment in the Nodinite Portal (Servers step).

Option: Service Bus Relaying (cloud or hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on different networks. Both sides connect outbound to the Azure Relay namespace, so neither server needs an inbound rule. Nodinite uses the same principle as the on-premises data gateway; see 'Adjust communication settings for the on-premises data gateway' and the 'Azure Relay FAQs'.

Between the Log File Parser Monitoring Agent and the log file folders

Required when the log files are on a Windows file share or a Samba share.

Tip

Log File Locations: Grant the agent service account Read permissions on all target folders and their child folders (if the 'Include child folders' option is enabled).

Between the Log File Parser Monitoring Agent and the Domain Controller

Required when the agent's service account is a domain account or gMSA that accesses the SMB shares.

Between the servers and DNS

Important

Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.

Next Steps

Install Log File Parser Monitoring Agent

Related Topics

Add or manage a Monitoring Agent Configuration
Monitoring
Administration