Observability 360 starts with full-stack alerting

You can’t fix what you don’t see

You’ve instrumented your backend. CPU, memory, and response time. Check ✅.
You’ve got alerts firing when a server starts to sweat or throughput takes a dive. Check ✅

But despite all that coverage, users are still reporting slowness. So you check the logs. Then the traces. Then the database. Everything looks… fine?

And that’s the problem. When your alerts only watch the backend, you’re only seeing part of the picture. Because performance isn’t just what happens on the server, it’s what your users experience in the browser.

Backend metrics give you reliability. Browser metrics give you reality.

Let’s say your servers are responding in under 100ms. Feels fast, right? But what if your users don’t see anything paint on screen for another 2.5 seconds? Or what if the layout jumps around just as they’re about to click a button?

These are real-world issues that affect conversion, engagement, and user happiness. They’re also invisible to most alerting setups. Until now.

Introducing: full-stack alerting in Blackfire

We’re excited to announce that Browser Monitoring metrics are now accessible within Blackfire’s alerting system, right alongside backend indicators like Response Time, Memory, and Load.

You can now trigger alerts based on:

• Time to First Byte (TTFB)
• First Contentful Paint (FCP)
• Largest Contentful Paint (LCP)
• Cumulative Layout Shift (CLS)
• Interaction to Next Paint (INP)
• Browser Throughput

This means you can get alerted not only when your app breaks, but when it starts to feel slow, or worse, annoying, for real users.

Why this matters: building toward Observability 360

At Blackfire, we believe observability should span your entire application lifecycle, from the backend logic to the browser’s rendering pipeline. We call this vision Observability 360.

This release marks a critical milestone in that journey:

• It bridges the traditional gap between dev teams, from DevOps to API and frontend teams.
• It surfaces user-facing issues before users complain.
• It lets you unify your performance strategy, one alerting system, one platform, full context.

Think of it as bringing together perceived performance and system performance under one roof.

Start small, think big

You don’t need to overhaul your entire observability strategy overnight. Start by adding a few key browser alerts:

• Alert when LCP exceeds 2.5s on your homepage.
• Alert when Cumulative Layout Shift > 0.1 spikes after a release.
• Alert when Interaction to Next Paint climbs in your checkout flow.

These small steps can reveal performance regressions you wouldn’t catch otherwise, and help you ship smoother, faster experiences with confidence.

Ready to take your alerts to the frontend?

If you’re already using Blackfire, it’s just a matter of opening the alerting dropdown and selecting your favorite browser metric.

Not using Browser Monitoring yet? Learn more here.

Let’s build better digital experiences by observing everything that matters.

To better observability and beyond