In this video, I show you how you can leverage our pre-built dashboard templates and widget library to build your dashboard that will set your team up for success in under 5 minutes!

With millions of monthly active users across Bitbucket and Jira, Atlassian relied heavily on the real-time telemetry they got from their open source instance of Sentry. However, because it took the equivalent of two full-time engineers to maintain their out-of-date instance, Atlassian started to explore paths to upgrade or migrate to SaaS, as the risk of things breaking increased with each new release.

In this video, we do a spin off of one of our favorite shows Hot Ones, where we combine an interview with Web Platform Team Technical Project Manager Steven and our Web Platform Team EM Vladan, and hot sauces. Meet both of them in this in this video, and watch them suffer as they go from one hot sauce level to the next just like they do in Hot ones.

Business is booming – your team is growing, your customer base is expanding, and you’re shipping more than ever. But without the right processes in place to scale, that fast-paced growth can leave engineering teams scrambling to navigate an increasingly more complex codebase, new team structures, and an ever-growing backlog of issues and requests. Join Jad Chamoun, Engineering Manager at Forethought, as he walks through how Forethought increased developer autonomy and workflow efficiency so their growing team can triage issues quickly without playing the blame game.

Join Simon Zhong, Sentry Sales Engineer, as he goes through setting up Sentry step-by-step to get visibility into our frontend and backend. Once integrated, he will track and triage errors + transactions surfaced by Sentry from our services to understand why/where/how errors and slowdowns occurred within our application code. This workshop took place live at DevOps.JS Conference on March 21, 2022.

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.