Operations | Monitoring | ITSM | DevOps | Cloud

Change Happens - Get Alerted

To give you enough notice to fix an issue before it escalates, we’re evolving our alerts and making them more proactive with Change and Crash Rate Alerts. So when your application experiences a change from the norm or a dip in crash-free sessions, Sentry will (smartly) alert you via Slack, Teams, PagerDuty, or old-fashioned email.

How LogicMonitor Can Use Errors From Airbrake in Dashboards and Alerts

LogicMonitor continues to grow its visibility of critical business infrastructure and applications. We acquired Airbrake to help see more of what is happening in a customer’s environment at the code level. Simply integrating Airbrake’s dashboard metrics within LogicMonitor alongside your existing networks, services, and cloud infrastructure enables you to gain access to errors and the context you need to effectively troubleshoot issues impacting your systems and users.

Debug Android crashes faster with Datadog

Technical issues, such as fatal crashes, are one of the biggest reasons why users uninstall mobile applications, so quickly identifying and resolving issues is vital for user retention. This can be challenging, particularly in the Android market, which has a wide variety of mobile devices and versions of the Android operating system. You need visibility into every issue so you can determine which crashes impact your application the most and efficiently resolve them.

How to start error tracking with Rollbar

Rollbar is an error tracking product that monitors your applications for errors and helps you take action on them. Rollbar also integrates with other products so you can send the errors to project management tools, incident alerting tools etc. In this post, we will show you how to get started with error tracking using Rollbar.

Getting started with Raygun Crash Reporting using Raygun4Android

Building native mobile apps can be a daunting challenge. Even if you ignore the choice of building separate iOS/Android apps or using cross-platform technology, writing native apps is hard. The development process of native apps involves a lot of testing and debugging. While the app is still under initial development this usually happens on test devices of the developers or dedicated testers. When problems arise or the app crashes, these incidents are often observable and can be debugged.

Close the Loop with User Feedback

Everyone’s software crashes. As an engineer, you don’t feel your users’ frustration unless they reach out to customer support, write bad reviews, or tweet about it. This feedback is often lacking relevant information to resolve the issue. In some cases, you can re-engage with the customer, but that process is time-consuming and inefficient. Another option would be to examine the crash reports, but sometimes they don’t give sufficient insight to fix the problem.