Get a DemoStart Free TrialSign In


Ship logs from your .NET application to logstash

Follow this step by step guide to get 'logs' from your system to

Step 1 - Install

You can ship logs from .NET and MONO applications using common logging frameworks. We have documentation for:

  • Serilog configuration
  • NLog configuration
  • log4net configuration
I'm choosing a framework, which should I use? We recommend Serilog as it has structured logging support.
I can't use Serilog, NLog or Log4net! If you are not using a framework listed above there are a number of options you can consider:

- Log to file and use Filebeat to ship logs
- Modify logging framework to output to HTTP
- Modify logging framework to output to TCP

Step 2 - how to diagnose no data in Stack

If you don't see data appearing in your Stack after following the steps, visit the Help Centre guide for steps to diagnose no data appearing in your Stack or Chat to support now.

Step 3 - Check for your logs

Now you should view your data:

View my data

If you don't see logs take a look at How to diagnose no data in Stack below for how to diagnose common issues.

Step 4 - .Net Logging Overview

.NET is a free development framework created by Microsoft that allows for easier application engineering. The framework provides an environment for programmers to use throughout the software development process.

.Net is compatible with multiple libraries, editors and programming languages including F#, PowerShell, Visual Basic and IronPython.

By default .Net only works on Windows devices, unless you use a tool like Mono to make .Net compatible with your Linux device. If cross operating system compatibility is a concern for your development process then you’ll likely prefer using .Net Core as a framework of choice.

When .Net encounters an error these log files can be found by inspecting the Windows event log. .Net is associated with a number of log types including, security, application, OS, and IIS logs (as .Net applications typically run on IIS Servers.

Among these log types you’ll also find statuses on the applications log events, in reverse severity these include Error, Warning & Information.

With all these logs being generated by a single development framework, it can be difficult to identify and visualise which of your .Net logs may be of highest importance when it comes to spotting errors and creating security reports.

Thanks to our log viewer and ELK as a Service offering, makes parsing and managing your logs from .Net effective. Our platform is able to centralise all of your log data across tools, platforms and services that you use on a daily basis.

If you need any more assistance in analysing your .Net logs we're here to help. Feel free to get in touch by reaching out to our support team via Intercom and we will be happy to assist.

Return to Search
Sign Up

© 2023 Ltd, All rights reserved.