CODEWITHSUNDEEP
c#asp.netlogging
Diego Jancic
Diego Jancic

Reputation: 7440

What is a good place to store production logs of an ASP.NET application?

Environment: Windows instance hosted in AWS. ASP.NET application logs events and errors using log4net to an SQL Server database.

Now I'm looking to offload that logging to another server with the final goal of 1) reducing the load on the SQL Server and the server itself and 2) have a better way to search and analyze those logs, which are currently being stored in a non-indexed table.

I’m looking for something faster yet simple to install, configure and use. I've already investigated Seq, Logstash, and others, but none seem to fit my requirements very well. Can you suggest a solution?

The requirements:

The good to haves:

Upvotes: 1

Views: 615

Answers (1)

driis
driis

Reputation: 164301

One option is Elasticsearch and Kibana. Use Google, but a good starting point for you could be http://www.ben-morris.com/using-logstash-elasticsearch-and-log4net-for-centralized-logging-in-windows/

The idea behind putting the logs in a search engine instead of into a database; is to make it easier to search your logs. You will get indexing on the fields you choose and full text search for free here. At the same time, Kibana provides an excellent user interface for exploring and aggregating logs.

My personal experience is that this makes for a very good logging setup that will make it easier for you to spot errors and negative trends faster.

Upvotes: 1

Related Questions