- 4 minutes to read

Release Notes
Prerequisites for the Nodinite Log File Parser Monitoring Agent

This page describes the prerequisites 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

Please use RegEx101 or a similar tool, to test your RegEx expression. You must practice RegEx in order to use this agent.

Instances of this agent can be installed on-premise using TCP/IP for local network access and/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
Windows Server 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 make use of the .NET Framework 4.8 or later.
Versions 5.4 and subsequently make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.

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

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

least privileges (basic usage)

  • Read permission to the folder where 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 has 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

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

The following ports must be allowed on the Windows server where the agent is installed and running:

Port Name Inbound Outbound TCP UDP Comment
53 DNS 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 1 (Local network)

Port Name Inbound Outbound TCP UDP Comment
8000 RPC Communication is initiated by the Monitoring Service

Option 2 (Cloud/Hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on totally 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.

The following ports must be open 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 Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

2. Between the Log File Parser Monitoring agent and folder locations

Additional firewall requirements may exist depending on the usage of the Samba protocol, Certificates, NTLM, Kerberos, Sun RPC...

SMB

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide
135-139 SMB Microsoft file sharing SMB
445 SMB Direct-hosted SMB traffic

Next Step

Install Log File Parser Monitoring Agent

Add or manage a Monitoring Agent Configuration
Monitoring
Administration