Slide 2 of 5

Where integrations fit

Observability builds in layers

Hierarchy of Observability Needs

LevelFocusQuestion Answered
Level 1Infrastructure“Is my server healthy?”
Level 2Services“Which service is the problem?”
Level 3Transactions“Why is this request slow?”
Level 4Custom logic“What’s happening in my code?”

Integrations give you Level 1 observability

You can’t troubleshoot services if you don’t know your infrastructure is healthy. Integrations build that foundation.

Script

Before we dive into integrations, let’s zoom out and understand where they fit in the bigger picture.

Observability isn’t one thing. It’s a hierarchy of needs. At the foundation, Level 1, you need infrastructure visibility. Can you see if your servers, databases, and networks are healthy? This is the base everything else builds on.

At Level 2, you shift focus to services. Which service is causing the problem? At Level 3, you dig into individual transactions. Why is this specific request slow? And at Level 4, you add custom instrumentation for application-specific questions.

Here’s the key insight: integrations give you Level 1. They’re the fastest path to infrastructure visibility. Pre-built dashboards, alerts, and data collection for the systems you’re running.

You can’t troubleshoot service issues if you don’t know your infrastructure is healthy. Integrations build that foundation. That’s why we’re starting here.

/
Previous Next