Debugging and resolving incidents in nodeless environments can be difficult, time-consuming, and most of all, frustrating. Exporting your logs from these ephemeral and disparate services to a centrally aggregated log is a great way to correlate information, quickly resolve incidents, and make your life a little easier.
In this post, we’ll look at the process and benefits of exporting logs from a nodeless environment such as AWS EKS on Fargate to a central cloud solution using SolarWinds® Papertrail™ and rKubeLog.
The SolarWinds® Papertrail™ team is excited to announce SolarWinds rKubeLog, an open-source project designed to streamline Kubernetes logging. rKubeLog allows you to forward logs to Papertrail from within a Kubernetes cluster without using a daemon or setting up application-level logging or a logging sidecar.
When you’re troubleshooting, issues seem to fall into two categories: issues based on an alert or error message where you have a good idea where to start and ones where you have no idea what’s going on. The first issues are usually straightforward. You use the information provided in the alert or error message to search the logs and pull up the relevant event messages. By searching a little more and exploring the context around the events, you can deduce the cause of the problem and start remediation.
The second type of issues—the ones where the error message is vague, or the alert doesn’t provide additional details—is more difficult.
Infrastructure is a complex and difficult concept for developers. When an issue occurs, where do you even begin to look?
I’ve spent years of my life playing the “What looks like one but not like the other” game, wrestling with confirmation bias and hunting through haystacks of logs to find a clue to my hosted applications. This takes away from time spent improving my applications—and it isn’t fun. “It’s probably the network…” isn’t enough to get the service back up to par. A good SRE needs tools to dive deeper.
Find and Fix Issues Before Your Users Notice a Problem
In a perfect world, how would like to learn about a problem?
From an angry customer call or email?
From your boss?
From a flaming Twitter post?
If you’re like the development team here at SolarWinds® Papertrail™, none of these options sound good. We’d all prefer to be notified when something starts to fail, but before there’s a service impact. At a minimum, we want to know the instant a service or application goes down. Fortunately, Papertrail has some powerful and easy-to-use alerting capabilities.
Looking for a new way to send logs to SolarWinds® Papertrail™? Now you can use HTTP.
As all Papertrail fans know, sending logs to Papertrail using syslog is quick and easy. Generating and transmitting syslog packets usually involves just 2 – 4 lines of code, and you can see your logs flowing into Papertrail in minutes.
SolarWinds® Papertrail™ now supports SAML v2.0, which makes Papertrail even faster and easier to access. Using SAML authentication you can log into your Active Directory domain or intranet and have immediate access to Papertrail, with no additional login required. The new SAML support also enables you to enforce user identity verification policies.
If you’ve been building or supporting applications for a while, you’ve probably experienced the uncomfortable postmortem meetings that inevitably follow significant service interruptions. You know how it works. There was a critical outage in one of your apps and it took the team an entire week to track down and fix the issue. Customers and revenue were lost.
Now you’re sitting in a large conference room with executives to discuss what happened and why.
The other day I found myself trying to tune a Ruby on Rails app I had written as a side project. (The app lets me keep track of my favorite eateries and pubs. It’s searchable, includes multiple images, and has stored locations.) On past projects, I relied on SolarWinds®Papertrail™, path testing, a lot of trial and error, and a general feel to try to improve performance. This time I thought I would give SolarWinds AppOptics™ Dev Edition a try.
I’ve never done much with application performance management (APM) tools. I heard they were hard to deploy and configure and pricey. With the announcement of AppOptics Dev Edition, which is designed to be quick to set up, integrated with Papertrail, and free for small pre-production environments, I thought I should give it a shot.