What do you use for logging?

Discussions
#1

I am working on a tool for use internally at my day job for logging. If I like using it and it’s helpful, I’d like to make it into a product. It’s basically a live view of your logs.

What do you use and what do you like/not like about it? Frameworks, SaaS, etc.

What do you log? web server logs, application logs, etc.

We use log4net (.NET SaaS company) among other things, but would like to learn what else is out there.

#2

I’m everything logging to: Trace, File and to a solution like LogEntries . Errors are also sent to a service like Raygun.io . I’m using Serilog (.Net) these days, it has sinks to everything I’m interested in.

1 Like
#3

I should try out LogEntries. Looks like a pretty mature product.

I had never seen Serilog, looks interesting.

Thanks for the reply!

#4

Serilog is ok but some sinks, like Raygun, have some issues.

#5

I’ve started using ELK stack - Elasticsearch, Logstash and Kibana for logs. Before that I’ve used Loggly, and also Splunk. I log web access and errors, app server access and errors, system level events (CPU, memory, disk I/O, login attempts, etc.) DB events, load balancers, firewalls, etc. Pretty much anything that might be useful in tracking down a bug.

Depending on the depth of your pockets, you can go crazy, so set the log level to something decent, and be sure to rotate periodically if you don’t want to pay out the wazoo for disk space.

#6

We send everything to Papertrail via rsyslog. The retention rate is relatively short though, so we also send our web application logs to LogEntries.

#7

couchdb-- for application level logs and file system for server logs.

I only log errors. Default server logs are stored on file system and automatically compressed by logrotate . For application level logs I store them on a separate database created for that purpose.

I also frequently analyse both application level and server level logs to check if any of the errors are being repeated and get rid of the old records.

#8

Thanks for all the responses guys. I have more methods and systems to investigate now!

#9

I’m using LogEntries to track Server Errors in real time from my Web App, Clibu. It is ok, but not great. I’ve documented what I’d really like and if I ever get time may develop something.

#10

I have done architecture design and implementation on ELK stack (logstash + elasticsearch + kibana). One thing, I will recommend, if you need logs to be captured for analysis or sharing, then always install Logstash (to be used as agent) on each instance. Then use Logstash output filters to send logs wherever you want to. (even to Logentries). By doing so, you will have flexibility to play around or switch around different log repositories by doing minor changes to already installed logstash config file.