- 2 minutes to read

Prerequisites for the Nodinite Log4Net Appender

This page describes the prerequisites for successfully running the Nodinite Log4Net Appender.

graph LR subgraph "Custom .NET based solutions" roNET1[fal:fa-code .NET Application] --> |Log4NET|roLA(fal:fa-comment-times Nodinite Log4Net Appender) roNET2(fal:fa-globe Web Service) --> |Log4NET|roLA roNET3(fal:fa-window-alt ...) -.-> |Log4NET|roLA end subgraph "Nodinite" roLogAPI(fal:fa-cloud-download Log API) roLA --> |Logging| roLogAPI roLogAPI --> roDB(fal:fa-database Log Databases) end

The Nodinite Log4Net Appender can be installed and configured with Log4Net enabled .NET applications on-premise using TCP/IP for local network access and/or in the cloud/off-site using with appropriate ports being opened to the Log API.

Verified Topic
Software Requirements
What Windows User Rights does the Log4Net Appender require?
What Firewall settings are required for the Log4Net Appender?

Software Requirements

The Log4Net Appender is a Windows Service and is usually installed on the Nodinite application server.

Product
Windows Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.5 or later

Supported Versions

Currently the Nodinite Log4Net Appender is built using the 2.0.8 version. Review the Apache Log4Net release notes for additional information.

Make sure to subscribe to our Release Notes

What Windows User Rights does the Log4Net Appender require?

The Nodinite Log4Net Appender is ultimately being executed on the thread of the .NET application. Since output from the Nodinite Log4Net Appender is posted to the Log API the only requirement is that the application is able to communicate potentially over the network. There may be firewall or other local policies involved.

What Firewall settings are required for the Log4Net Appender?

The Log4Net Appender has outbound communication only:

  1. Between the Nodinite Log4Net Appender and the Nodinite Log API
graph LR subgraph "Custom .NET based solutions" roNET3(fal:fa-window-alt ...) -.->|Log4NET|roLA(fal:fa-comment-times Nodinite Log4Net Appender) end subgraph "Nodinite" roLogAPI(fal:fa-cloud-download Log API) roLA --> |80/443/...| roLogAPI roLogAPI -.-> roDB(fal:fa-database Log Databases) end

1. Between the Log4Net Appender and the Log API

When Logging is enabled the Log4Net Appender requires one of the following outbound TCP ports to be open for access the Log Api (configurable)

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)
80 HTTP default for HTTP)
443 HTTPS default for HTTPS)

If the Log4Net Appender and the Log API is on the same server you should stick with http for performance and information is not outside the server


Frequently asked questions

Additional solutions to common problems and the FAQ for the Nodinite Log4Net Appender exist in the Troubleshooting user guide.

Next Step

Install the Log4Net Appender

Administration