- 4 minutes to read

Release Notes

Prerequisites for the Nodinite Log4Net Appender

Prepare your .NET Framework development environment to integrate the Nodinite Log4Net Appender NuGet package. This page outlines the software, network, and security requirements needed to successfully add centralized logging to your applications.

With this guide, you will:

  • ✅ Ensure your development environment is compatible with the NuGet package
  • ✅ Meet all network and security prerequisites
  • ✅ Enable robust, centralized monitoring and logging
  • ✅ Avoid common configuration issues

This page describes the prerequisites for using the Nodinite Log4Net Appender NuGet package in your .NET Framework projects.

graph LR subgraph "Visual Studio .NET Framework Projects" roVS[fal:fa-file-code Visual Studio] --> |NuGet|roLA(fal:fa-comment-times Nodinite Log4Net Appender) roNET1[fal:fa-code .NET Application] --> |Log4NET|roLA roNET2(fal:fa-globe Web Service) --> |Log4NET|roLA end subgraph "Nodinite" roLogAPI(fal:fa-cloud-arrow-down Log API) roLA --> |HTTPS| roLogAPI roLogAPI --> roDB(fal:fa-database Log Databases) end

The Nodinite Log4Net Appender is a NuGet package that you install in your .NET Framework projects using Visual Studio, Visual Studio Code, or the .NET CLI. Your applications can run on-premise using TCP/IP for local network access, or in the cloud/off-site with an appropriate network connection to the Nodinite Log API.

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

Software Requirements

The Nodinite Log4Net Appender is distributed as a NuGet package available on NuGet.org.

Nodinite.LogAgent.Log4NetAppender on NuGet.org

Development Environment

Product Requirements
Visual Studio Visual Studio 2019, 2022, or later
Visual Studio Code with C# extension
.NET CLI (dotnet.exe)
NuGet Package Manager Included with Visual Studio
NuGet CLI for command-line scenarios
.NET Framework .NET Standard 2.0 compatible
.NET Framework 4.6.2 or later
.NET Framework 4.7.2 or later (recommended)
Log4Net Apache log4net 2.0.8 or later (installed as dependency)

Runtime Environment

Product Versions
Windows Server Windows Server 2025
Windows Server 2022
Windows Server 2019
Windows Server 2016
Windows Server 2012 R2
.NET Framework .NET Framework 4.6.2 or later
.NET Framework 4.7.2 or later (recommended)
Azure Azure App Service
Azure Virtual Machines
Azure Container Instances (Windows containers)

Supported Versions

The Nodinite Log4Net Appender is built using the Apache log4net package from NuGet and targets .NET Standard 2.0. Please review the Apache Log4Net release notes for additional information.

Subscribe to Release Notes to stay informed about new versions and features.

What User Rights does the Log4Net Appender require?

The Nodinite Log4Net Appender executes on the same thread as your Log4Net-enabled .NET Framework application. The appender creates a Nodinite JSON Log Event and posts it to the Nodinite Log API over the network.

Required Permissions:

  • Network Access: The application must be able to make outbound HTTP/HTTPS requests to the Nodinite Log API endpoint
  • Application Permissions: The user account or service identity running the application must have standard .NET Framework execution permissions
  • No Special Privileges: No administrative or elevated privileges are required

Local firewalls or network policies may block outbound traffic to the Log API, so ensure appropriate firewall rules are configured.

What Firewall settings are required?

The Log4Net Appender requires outbound network communication only:

  1. From the application server to the Nodinite Log API
graph LR subgraph "Application Server" roNET(fal:fa-window-alt .NET App with Log4Net) -.->|Log4NET|roLA(fal:fa-comment-times Log4Net Appender) end subgraph "Nodinite Server" roLogAPI(fal:fa-cloud-arrow-down Log API) roLA --> |80/443/Custom| roLogAPI roLogAPI -.-> roDB(fal:fa-database Log Databases) end

1. Application Server to Nodinite Log API

Server types: Application Server (.NET Framework application with Log4Net Appender), Nodinite Server (Log API)

Log API Connection (Application → Nodinite Log API)

The Log4Net Appender sends log events to the Nodinite Log API for storage and analysis.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Application Server Nodinite Server (Log API) TCP 80 (HTTP), 443 (HTTPS), or custom port Log event submission Application posts JSON log events via HTTP/HTTPS
Inbound Nodinite Server Application Server TCP 80 (HTTP), 443 (HTTPS), or custom port Response traffic Allowed automatically by stateful firewalls

Tip

HTTPS Recommended: For production environments, configure the Log API to use HTTPS (port 443) with valid SSL/TLS certificates to encrypt log data in transit. Review the Hardening guide for security best practices.

Tip

Custom Ports: The Nodinite Log API can be configured to use any available TCP port. Verify the actual port in your Log API configuration and adjust the LogApiServiceURI setting in your log4net.config file accordingly.

Tip

Application Identity: The Log4Net Appender executes on the same thread as your .NET Framework application. Ensure the application's service account or user context has network access to the Log API endpoint.

Note

DNS Resolution: Application servers require outbound access to DNS on TCP/UDP port 53 for hostname resolution. You can optionally use entries in the local hosts file instead.

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.

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
Log API
JSON Log Event