- 6 minutes to read

Release Notes

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.

graph LR subgraph "Nodinite" roNI(fal:fa-code-commit Log File Parser) --- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "SMB Share B" roMonitor --- | Firewall/Security|roF2(fal:fa-folder Folder Y) roF2 --- ro2(fab:fa-java .log) roMonitor --- | Firewall/Security|roF3(fal:fa-folder Folder Z) roF3 --- ro3("fal:fa-file-csv .csv") end subgraph "SMB Share A" roMonitor --- | Firewall/Security|roF1(fal:fa-folder Folder X) roF1 --- ro1(fal:fa-file-alt .txt) end

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)

Verified Topic
Software Requirements
What Windows User Rights does the Log File Parser Monitoring agent require?
What Firewall settings are required for the Log File Parser Monitoring agent?

Software Requirements

Product Comment
Windows Server Windows 2025
Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later New 6.0
Our recommendation is .NET Framework 4.8.1 or later

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.

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?

The Nodinite Log File Parser Monitoring Agent requires both inbound and outbound communication:

  1. Between the Monitoring Service and the Nodinite Log File Parser Monitoring Agent
  2. Between the Nodinite Log File Parser Monitoring Agent and the Folders/SMB Shares with files to monitor
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roAgent(fal:fa-monitor-waveform Log File Parser Monitoring agent) roMonitoringService --> |8000/443| roAgent end subgraph "SMB Share A" roAgent --- | 135-139, 445|roF1(fal:fa-folder Folder X) roF1 --- ro1(fal:fa-file-alt .txt) end

Network diagram: The agent communicates securely with the Monitoring Service and SMB shares, ensuring reliable log file access and monitoring.

1. Between the Monitoring Service and the Log File Parser Monitoring agent

You must allow the following ports on the Windows server where the agent is installed and running:

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
53 DNS All The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)

And further with 'Option 1' or 'Option 2' as documented next:

Option 1a (Nodinite v7 - IIS hosted on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
Custom HTTP/HTTPS v7 Agent IIS site port (configured during installation in the Portal). Only required if agent is on a remote IIS server

Note

Nodinite v7 IIS Hosting: When agents are hosted in IIS on the same server as the Nodinite application (typical installation), firewall rules are not required between the Monitoring Service and the agent. The custom port is assigned during installation via the Nodinite Portal and only needs to be opened if the agent is hosted on a remote IIS Windows Server.

Option 1b (Nodinite v6 and earlier - Windows Service on local network)

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
8000 RPC v6 and earlier Communication is initiated by the Monitoring Service. Only used with legacy MSI installer on remote Windows servers

Note

Nodinite v6 Legacy: Port 8000 is only used when agents have default installations on remote Windows servers using the legacy MSI installer. This port is not required for Nodinite v7 IIS-hosted agents.

Option 2 (Cloud/Hybrid - All versions)

Use Service Bus Relayed connections when Nodinite and the agent are on different networks.

Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.

You must open the following ports for outbound communication with '*.servicebus.windows.net' from both on-premise and off-site (Nodinite Windows Server(s) and where the agent is installed):

Port Name Inbound Outbound TCP UDP Nodinite Version Comment
443 HTTPS All Secure outbound traffic
5671, 5672 Secure AMQP All
9350 - 9354 Net.TCP All

2. Between the Log File Parser Monitoring Agent and Folder Locations

Server types: Agent Server (where Log File Parser Monitoring Agent is installed), File Server (SMB file shares with log files).

Additional firewall requirements may exist depending on the use of the Samba protocol, Certificates, NTLM, Kerberos, Sun RPC, and other security technologies.

SMB Connection (Agent → Log File Folders)

The agent connects to Windows file shares or Samba-based services to monitor and parse log files.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server File Server (SMB) TCP/UDP 135-139 Microsoft file sharing (NetBIOS) Legacy SMB over NetBIOS
Outbound Agent Server File Server (SMB) TCP/UDP 445 Direct-hosted SMB traffic Modern SMB protocol (SMB 2/3)
Inbound File Server (SMB) Agent Server TCP/UDP 135-139, 445 Response traffic Allowed automatically by stateful firewalls

Tip

SMB Versions: Port 445 is used by SMB 2.0 and SMB 3.0 (recommended for security and performance). Ports 135-139 support older SMB 1.0/CIFS for legacy compatibility. Consider disabling SMB 1.0 for security.

Tip

Log File Locations: The agent monitors log files in specified folders. Ensure the agent service account has Read permissions on all target folders and their child folders (if 'Include child folders' option is enabled).

Note

DNS Resolution: All servers (Agent Server and File Servers) require outbound access to DNS on TCP/UDP port 53 for name resolution. This is already listed in section 1 and applies universally. You can optionally solve this using entries in the local hosts file on each server.

Important

Stateful Firewalls: Most modern Windows Firewall implementations are stateful, meaning inbound response traffic for established outbound connections is automatically allowed. The inbound rules listed above are primarily for reference and troubleshooting scenarios where stateful inspection may be disabled or restricted.

Next Step

Install Log File Parser Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration