By: Thu Nguyen
Read Time: 2 min
When launching an application into production, everyone knows that even the best code can fail for any number of reasons. Implementing strategies that enable you to quickly understand why something is failing and proactively identify the culprit will give you peace of mind and even let you catch some shut eye at night.
The first question developers are always faced with is, how much should I log?
Troubleshooting no longer just means looking at web server and infrastructure logs, but also custom application event logs, database logs, mail server logs, operating system logs, network logs, and so on. It’s tough to figure out where to look and how to correlate events with each other. Many late evenings are spent by weary DevOps teams grepping files on each server and watching dozens of shells running tail -f.
However, preventing these types of scenarios is where cloud log management solutions really shine. LogDNA’s agent allows you specify the logs you want to watch and you can not only watch them in real time, but also go back in time to see everything that happened. You can also set up views and alerts based on custom smart filters so that you can quickly identify and even prevent situations that have happened before.
Unfortunately most cloud logging solutions force you into deciding what to log right away by charging you on volume. LogDNA takes that question away by starting you off with 50GB/month – for free. There’s so much that goes into building and launching your application, don’t stress about optimizing how much to log on day 1.
This way you have time to figure out what logging events are significant and what views and alerts you need. As you troubleshoot your beta application issues, you’ll undoubtedly dig deeper and add more logging in certain areas and remove logging from others. Keep iterating, keep improving and keep delighting your customers.
Logging is probably not the first item to come to mind when most of us think about DevSecOps, a term that refers to the integration...
Isn't all logging pretty much the same? Logs appear by default, like magic, without any further intervention by teams other than simply starting a system…...
This was originally posted on The New Stack. Once upon a time, log management was relatively straightforward. The volume, types, and structures of logs were...