Pulse — APM Built for AI

Before

How Claude sees your app today

C

Claude

Y

You

The dashboard is loading slowly. Can you find what's causing it?

C

Claude

I'd like to help, but I don't have access to your performance data.

I can't see response times, database queries, or where time is being spent.

Could you share your APM dashboard or run some profiling?

Y

You

*Opens New Relic, waits for data to load, exports screenshots...*

After

How Claude sees your app with Pulse

C

Claude

Pulse connected

Y

You

The dashboard is loading slowly. Can you find what's causing it?

C

Claude

Let me check the dashboard performance...

Using pulse.get_slow_requests

pulse.get_slow_requests(path: "/dashboard", last: "1h")

Response

GET /dashboard avg: 4.2s (p95: 8.1s)

↳ SQL: 3.8s (12 queries)

↳ View: 0.3s

The database is the culprit. 12 queries taking 3.8 seconds. Let me trace one...

Using pulse.trace_request

pulse.trace_request(path: "/dashboard", slowest: true)

Trace

DashboardController#index

↳ Project.find(id) 2ms

↳ project.metrics 1.2s N+1

↳ project.team_members 2.4s N+1

Found two N+1 queries. project.metrics and project.team_members are loading separately for each project.

Solution: Add includes(:metrics, :team_members) to your query.

This will reduce 12 queries to 3 and cut load time to ~200ms.

Diagnosis time: 45 seconds

The Difference

Without Pulse

— Claude can't see response times
— You export APM dashboards manually
— Hours correlating traces and code
— Performance regressions go unnoticed

With Pulse

+ Claude sees every request, every trace
+ Full breakdown: SQL, views, external calls
+ AI spots N+1s and slow queries instantly
+ Concrete fix suggestions with code

How It Works

1

Every request is traced

Pulse instruments your app automatically. No code changes needed.

GET /dashboard 4.2s · 12 queries · 3 views

2

AI detects anomalies

Baseline learning spots when something slows down.

/dashboard slowed by 3.2x

Detected 15 minutes after deploy

3

Deep traces available via MCP

Claude can drill down into any request, any span, any query.

pulse.trace_request (path: "/dashboard", slowest: true)

4

AI suggests the fix

Not just "this is slow"—actual code changes to make it fast.

Add includes(:metrics) to fix N+1

The Tools AI Uses

Available via MCP (Model Context Protocol)

pulse.get_slow_requests()

"What's running slow?"

pulse.trace_request(path)

"Break down this request"

pulse.get_queries(slow: true)

"Show slow database queries"

pulse.compare_deploys()

"Did this deploy slow things down?"

Get Started

One gem. Zero config. Works in 30 seconds.

# Add to your Gemfile

gem 'brainzlab'

# Run bundle

$ bundle install

# That's it. Performance is being tracked.

Coming Soon

We're building Pulse right now. Follow along to get early access and help shape the features.

Follow the Journey View All Products