Slide 2 of 4

Why Level 4?

The key question

“What’s happening in my application logic?”

Problems you can solve at Level 4

ProblemHow Level 4 helps
“How many orders were placed this hour?”Custom application metrics
“What’s our checkout conversion rate?”Application-specific counters
“Why did this specific calculation fail?”Custom spans with application context
“What was in the user’s cart when they abandoned?”Enriched trace attributes

Who needs Level 4

Teams that need to answer questions auto-instrumentation can’t:

  • Revenue impact of outages
  • Feature-specific performance
  • Application workflow bottlenecks

Script

Auto-instrumentation is powerful, but it only sees what it’s designed to see: HTTP requests, database calls, framework operations. It has no idea what your application logic is doing.

Level 4 fills that gap. How many orders were placed this hour? What’s our checkout conversion rate? Why did this specific discount calculation fail? What was in the user’s cart when they abandoned it?

These are application-specific questions, and answering them requires custom instrumentation.

Level 4 is for teams that need to answer questions auto-instrumentation can’t: What’s the revenue impact of this outage? Which feature is causing performance problems? Where are the bottlenecks in our application workflows?

/
Previous Next