In A Comedy of Errors, we talk to engineers about the weirdest, worst, and most interesting application and infrastructure issues they’ve encountered (and resolved) over the years. This week, we hear from Jason Dufair, Full Stack Developer on the Studio team at Purdue University.
In mobile apps, it’s important to monitor errors so you can understand your user’s experience. Your team should know quickly when there are problems with the app itself or your backend services so you can fix the issue before more customers are affected. We’ll show you how to handle errors in iOS apps. We’ll then show you how Rollbar error monitoring can give you better visibility into errors and help you troubleshoot them faster.
Increasingly more software teams - ourselves and our customers included - are adopting practices like microservices and/or Continuous Delivery. We built the All Items View to make error monitoring much easier for those using Rollbar in such ways.
Logging is an important part of understanding the behavior of your applications. Your logs contain essential records of application operations including database queries, server requests, and errors. With proper logging, you always have comprehensive, context-rich insights into application usage and performance. In this post, we’ll walk through logging options for Rails applications and look at some best practices for creating informative logs.
In a previous post, we walked through how you can configure logging for Rails applications, create custom logs, and use Lograge to convert the standard Rails log output into a more digestible JSON format. In this post, we will show how you can forward these application logs to Datadog and keep track of application behavior with faceted log search and analytics, custom processing pipelines, and log-based alerting.
Accountability is an important part of the work IT professionals do, especially when it comes to security and outages. A minor change by a single tech or engineer can crash entire systems, and it’s sometimes crucial to question that person on their methods and changes to determine a solution. Accountability is especially important when several people are regularly using the same tool.
Application Performance Management (APM) tools are hot right now - so much so that it won't be long before APM reaches the same level of notoriety as the cloud, the IoT, and a personal favourite - big data.
Here’s the next installment in our Mattermost Recipes series. The goal of these posts is to provide you with solutions to specific problems, as well as a discussion about the details of the solution and some tips about how to customize it to suit your needs perfectly.
Today we are releasing Grafana 5.2.3 and Grafana 4.6.4. These patch releases includes a very important security fix for all Grafana installations which are configured to use LDAP or OAuth authentication.
In some performance critical situations, it makes sense to limit management software to a single CPU (core). We can do this using systemd and cgroups. CFEngine already provides systemd units on relevant platforms, we just need to tweak them. I’m using CFEngine Enterprise 3.12 on CentOS 7, but the steps should be very similar on other platforms/versions.
