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.

Design applications to be modular. It’s a software design best practice. Modular programming is writing multiple independent programs that perform a single function but work together to achieve an overarching outcome. The benefit to this design is the smaller parts can be easily created and tested. New functionality can be slipped into the larger whole without interfering with other functions.

Hidden among your normal, everyday logs are any number of unexpected events and anomalies. These events can provide key insights when troubleshooting problems, tracing transactions, or monitoring performance and behavior. However, finding them can be challenging, especially if you’re unsure of what, or how, to look for them. Searching for unexpected events involves more than just searching for keywords like “error” or “critical”.

Teams switching from a monolithic application architecture to microservices often face a jarring realization: their time-tested troubleshooting techniques don’t work as effectively. A microservice consists of many independent, distributed, and ephemeral services with varying capabilities for monitoring and logging. Techniques such as stack traces are effective troubleshooting tools in monoliths, but only paint a small portion of the big picture in a microservice-based application.

If you’ve visited the SolarWinds® Papertrail™ event viewer this week, you may have noticed it’s roomier. There’s less scrolling needed and more of the log line appears on the screen. You may be wondering what changed. Based on suggestions from user feedback, we streamlined the navigation and tucked it into the top bar. This change lets the logs message fill the entire screen width and lets you see more of the log message, with less scrolling.