Prerequisites for the Nodinite Log4Net Appender

Prepare your .NET applications for seamless, secure, and scalable logging with the Nodinite Log4Net Appender. This page outlines everything you need to get started, including software, user rights, and network requirements.

With this guide, you will:

✅Ensure compatibility with your .NET environment ✅Meet all security and network prerequisites ✅Enable robust, centralized monitoring and logging ✅Avoid common pitfalls and configuration issues

This page describes the prerequisites to make the Nodinite Log4Net Appender operational for Logging and Monitoring scenarios.

The Nodinite Log4Net Appender can be installed and configured with most Log4Net-enabled .NET applications. These applications may exist on-premise using TCP/IP for local network access or in the cloud/off-site, using an appropriate port with an open connection with the Nodinite Log API.

Software Requirements

The Nodinite Log4Net Appender is a NuGet package (a .DLL), and you embed it together with your application/solution.

Package on NuGet.org

Supported Versions

The Nodinite Log4Net Appender is built using the Log4Net package from NuGet. Please 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 executes on the thread of the Log4Net-enabled .NET application. The data, a Nodinite JSON Log Event, gets posted to the Nodinite Log API. The application must be able to communicate potentially over the network. There may be firewalls or other local policies involved that may block this traffic.

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

1. Between the Log4Net Appender and Nodinite Log API

Server types: Application Server (custom .NET 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.

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 Log4Net Appender settings accordingly.

Tip

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

Note

DNS Resolution: All servers (Application Server and Nodinite Server) require outbound access to DNS on TCP/UDP port 53 for name resolution. 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.

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

Related Topics

Administration