Operations | Monitoring | ITSM | DevOps | Cloud

When it comes to debugging a performance issue, being able to pick out slow spans (operations or “work” taking place on your service) out of a lineup is the fastest way to see the root cause and know how to solve it.

When it comes to debugging a performance issue, being able to pick out slow spans (operations or “work” taking place on your service) out of a lineup is the fastest way to see the root cause and know how to solve it.

Suspect Spans surfaces a list of spans that correspond to where the most time in a transaction is spent. Instead of clicking into every trace in an attempt to identify the bad actor, check out the Spans tab or Suspect Spans section in every transaction summary and jump directly to the span that needs your attention. In this video, we dive more into what suspect spans are, and we go through a demo of how you can also use Suspect Spans as a complement to your performance monitoring.

In this video, I delve with you into what distributed tracing is, and we dive into a quick demo to show you how to use this in your project.

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.

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.

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.

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.

These are actual videos submitted by Sentaurs for our monthly Show-N-Tell. We have not edited them except for obscuring personal information that may appear in screenshots. Some videos may include screenshots that contain fictitious usernames or email addresses for illustrative purposes.

These are actual videos submitted by Sentaurs for our monthly Show-N-Tell. We have not edited them except for obscuring personal information that may appear in screenshots. Some videos may include screenshots that contain fictitious usernames or email addresses for illustrative purposes.