Technical Resources
Educational Resources
Connect with Us
At Papertrail we are software engineers who are passionate about programming, debugging, logging and pretty much everything about building and running applications. We enjoy keeping our coding skills sharp and playing with new technologies. Below are some of things we have picked up along the way.
Fully Functional for 14 Days
Last updated: September 2024
Node.js may be the run-time environment that lets you use a single programming language (JavaScript) for both server-side and client-side applications, but it has no shortage of logging methods. Even though there are clearly delineated trade-offs with each of the logging techniques, if you’re a newcomer, it can be difficult to make sense of them and to know which one is right for your environment.
Last updated: September 2024
As an IT professional, you’ll find log messages are one way to catch errors and solve your problems. As much as log messages are helpful, they can be confusing because a lot of messages—even the log messages you don’t need to see—are generated by the server. Instead of making your life easier, log messages can make things harder for you because unnecessary error messages are being logged.
Last updated: September 2024
Logs are a ubiquitous component of IT. They come in all shapes and sizes from a wide variety of sources and possible destinations. But at the end of the day, all types of logging serve a fundamental role in a technological infrastructure: they allow a system to record information about its behavior to a persistent medium. People can then look at this information and reconstruct what happened so they can detect and fix whatever issues they might find.
Last updated: September 2024
Routers play a key role in any network. If you’re like most network engineers, you usually spend most of the time working with routers (as opposed to other network devices). In smaller networks, routers may even be the only devices managing traffic. Router logs can tell you a lot about your network. In this post, we’ll walk through how to analyze router logs efficiently.
Last updated: September 2024
Logging is crucial in software development, so it’s vital to get it right. That’s easier said than done, unfortunately. Application logging—Python logging included—is riddled with traps you might fall prey to if you aren’t careful.
But you can’t beware what you don’t know, and that’s where this post comes in handy. We’re here to warn you about eight of the most common logging pitfalls in Python. You’ll learn about each problem and techniques and tools you can use to avoid it.
Last updated: August 2024
There are many methods to help you avoid bugs in your application. You can use linters, write tests, or use an IDE, which will help you spot bugs early in the coding phase. However, no matter how good you are at preventing bugs, they will always happen. And it may not have anything to do with you. You could get hit by a bug in the third-party library you use. Therefore, as important as bug prevention is, it’s also crucial to know the debugging process well.
In this post, you’ll learn how to debug Ruby on Rails applications.
Last updated: August 2024
Like most developers, you’ve seen the benefits of logging first-hand—the right log message can be the key to unlocking the trickiest of software issues. However, not all logging is created equal, and actionable logs don’t magically appear. If you want the best logs, you must optimize your approach using tried-and-true best practices.
In this article, we’ll look at ways to improve your .NET error logging and make it easy to write logs containing vital information to help you troubleshoot your .NET apps and services.
Before diving into optimizing your .NET error logging, make sure you have the following prerequisites in place:
Basic Knowledge of .NET Framework: Understand the .NET framework and how to integrate logging libraries into your applications.
Understanding of Logging Concepts: Familiarize yourself with logging concepts, including log levels, log messages, and log destinations.
Last updated: August 2024
Server logs are essential and can never be left out of web development. There’s no such thing as a perfect website—even one owned by a big tech company is likely to have errors in production. Using web server logs, you can easily know where the problem is coming from and solve it on time. Hence, they are quite important when monitoring and filtering your web server.
In this post, I’m going to talk about what web server logs are, why you need to log your website page, how and the various types of logs. Moreover, I will also provide practical tips on monitoring and filtering web server logs using not just the Tail and egrep Commands but also the NGINX Server and get the most value out of them.
Last updated: August 2024
If your application uses Ruby, there are multiple ways to write log messages, each with various degrees of ease-of-use and control. Yet all these methods come with known issues that can derail your attempts to diagnose software issues and assist your Ruby troubleshooting.
If you’re knee-deep in Docker containers (like most of us these days), you know the drill: something goes sideways, and it’s up to us to play detective. The first place we’re diving? The logs, specifically those last 100 lines where the juicy bits hide.
Fully Functional for 30 Days
Contact our team, anytime.