Operations | Monitoring | ITSM | DevOps | Cloud

Sentry

How Monday.com Accelerates Time to Triage with Code Observability

Monday.com was on a mission to better aggregate and manage server errors for their monolith backend. But, what started as a minor change turned into a “life-changing decision”—their words, not ours—to incorporate a whole new workflow for frontend, backend, and soon mobile. Join Software Engineer Roni Avidov as she explains how Monday.com started monitoring their client-side app alongside their backend to quickly uncover blindspots and accelerate time to resolution by nearly 20 minutes per issue.

Building an Always-on Business Leaves No Room for Downtime

As is often the case with digital products, your users could be experiencing issues you might not be aware of. The unknown unknowns could include random bugs or memory leaks slowing down performance and, in many cases, those issues aren’t reported… folks just bail. If uptime is a core tenet of your business success, unreported issues and users moving on to the next best thing isn’t an option.

Continuous Performance Improvement of HTTP API

The following guest post addresses how to improve your services’s performance with Sentry and other application profilers for Python. Visit Specto.dev to learn more about application profiling and Sentry’s upcoming mobile application profiling offering. We’re making intentional investments in performance monitoring to make sure we give you all the context to help you solve what’s urgent faster.

Distributed Tracing and Suspect Spans

At the root of every performance issue is, there is most often a single event that creates a domino effect of excruciatingly slow load times. With distributed tracing, we give you all the context to see what actually matters and help you solve what’s urgent faster. However in some cases, you might want or like really need a short cut. And this is where Suspect Spans come into play.

How we optimized Python API server code 100x

Python code optimization may seem easy or hard depending on the performance target. If the target is “best effort”, carefully choosing the algorithm and applying well-known common practices is usually enough. If the target is dictated by the UX, you have to go down a few abstraction layers and hack the system sometimes. Or rewrite the underlying libraries. Or change the language, really. This post is about our experience in Python code optimizations when whatever you do is not fast enough.

Tracking Stability in a Bluetooth Low Energy-Based React-Native App

For most of my career I’ve worked with health and wellness startups. Most of these companies have a wearable that tracks movement, heart rate, body weight or stimulates a body part. The common denominator between these apps is their use of sensor data to determine physiological progress an athlete is making. Problem is, your Bluetooth Low Energy (BLE) device does not have an internet connection and cannot send diagnostics anywhere if there are errors.

Node Congress Lightning Talk: Monitoring errors and slowdowns with a JS frontend and Node backend

We've got a JavaScript frontend hitting a Node (Express.js) backend. Join Chris Stavitsky in this quick 7-min demo as he goes through how to know which party is responsible for which error, what the impact is, and all the context needed to solve it. This lightning talk took place at Node Congress on Feb. 17, 2022.

Node Congress Workshop: Tracking errors and slowdowns in Node + JavaScript using Sentry

Join Neil Manvar, Sales Engineer Manager, as he sets up Sentry step-by-step to get visibility into our frontend and backend. Once integrated, he will show you how to track and triage errors + transactions surfaced by Sentry from our services to understand why/where/how errors and slowdowns occurred within the application code. This workshop took place live at Node Congress on February 15, 2022.