In the high-stakes world of Site Reliability Engineering (SRE) and DevOps, time is the most expensive commodity. When a mission-critical service goes offline at 2:00 AM, engineers are often thrust into a chaotic scramble, navigating a labyrinth of fragmented browser tabs, disconnected telemetry streams, and static documentation. Today, New Relic has officially announced the General Availability of New Relic Notebooks, a transformative data exploration capability designed to unify the troubleshooting experience, foster team collaboration, and replace static post-incident reports with living, breathing data narratives.
Available at no additional cost for all Full Platform Users, Notebooks represent a strategic shift in how observability data is consumed, analyzed, and communicated across engineering organizations.
The Anatomy of the Announcement: What Are New Relic Notebooks?
At its core, New Relic Notebooks is a multi-cell, structured workspace integrated directly into the New Relic platform. It allows engineers to combine live NRQL (New Relic Query Language) queries, dynamic visualizations, and rich Markdown text into a single, cohesive document.
Unlike traditional dashboards, which provide a "snapshot" of system health, Notebooks act as a canvas for investigation. They allow for sequential drill-downs, where an engineer can document the logic behind an investigation while simultaneously executing the queries necessary to prove or disprove a hypothesis. By preserving the exact time-bound context of an incident, Notebooks ensure that the "why" behind an engineering decision is as visible as the "what" of the system performance metrics.
Chronology of a Crisis: Why the Status Quo is Broken
To understand the necessity of this tool, one must look at the standard lifecycle of a modern infrastructure incident. The "tab fatigue" phenomenon described by industry veterans is not merely a nuisance; it is a critical bottleneck in Mean Time to Resolution (MTTR).
1. The 2:00 AM Alert
An SRE receives a page. The incident begins. The engineer logs into their observability platform, initiating a query to identify the spike in error rates.
2. The Fragmented Search
The initial query raises more questions than answers. The engineer opens a second tab to look at latency, a third to check database health, and a fourth to examine recent deployments. Context is lost as the engineer flips between windows, often manually copying and pasting values into a scratchpad.
3. The "Dead Data" Hand-off
Once the root cause is identified, the labor-intensive process of reporting begins. The engineer takes screenshots of their charts, pastes them into a Confluence page or a Slack thread, and writes a narrative around them. By the time the team reads the report, the data is static—"dead." If a stakeholder asks, "What happened if we filtered by this specific region?" the engineer has to restart the entire investigative process.
New Relic Notebooks exist to collapse this timeline. By keeping the investigation, the documentation, and the live data in one persistent file, the platform eliminates the "dead data" gap entirely.
Supporting Data: The Cost of Cognitive Load
Industry research has consistently shown that the cognitive load placed on SREs during an outage is a leading cause of burnout and delayed resolution. According to recent internal metrics from New Relic, the time spent "context switching"—the process of moving between tools and tabs—accounts for nearly 40% of the time engineers spend investigating incidents.
By consolidating the workspace, Notebooks address the following pain points:
- Information Silos: Data remains trapped in the browser history of an individual engineer. Notebooks allow these investigations to be saved as collaborative assets.
- Context Decay: When an investigation is interrupted or handed off to another team, critical mental models of the system are often lost. A Notebook acts as a permanent record of the investigative path.
- Knowledge Transfer: Junior engineers often struggle to understand the "why" behind a fix. Notebooks serve as an educational library where senior engineers can document their logic, effectively turning complex troubleshooting sessions into training modules.
Official Perspectives: Empowering the Engineering Narrative
Joanna Pacek, Senior Product Manager at New Relic, has been the primary architect behind the development of Notebooks. Her focus has been on bridging the gap between "technical troubleshooting" and "organizational knowledge."
"We built New Relic Notebooks because we saw a fundamental disconnect in how teams work," says Pacek. "The tools we use to monitor systems have evolved, but the tools we use to share our findings have remained stuck in the era of static documents. With Notebooks, we are enabling teams to tell the full story of their data, transforming the investigative process into a persistent, collaborative narrative."
Pacek emphasizes that the tool is not just a reporting feature; it is an analytical instrument. By allowing users to pipe results from one query into another, the platform enables complex, automated workflows that were previously impossible without custom-built scripting tools.
Implications: Transforming Core Engineering Practices
The introduction of Notebooks is poised to change three specific domains of engineering work:
I. Advanced Root-Cause Analysis (RCA)
Instead of relying on memory, engineers can build a logical sequence of cells. Cell one might establish a high-level query; cell two filters by a specific microservice; cell three compares the current anomalous latency against a baseline from the previous week. This structure forces a methodical approach to troubleshooting, reducing the likelihood of "guessing" the cause of a service failure.
II. The Evolution of Post-Mortems
Post-incident reviews are often criticized for being "post-incident" in name only—they are often vague, retrospective summaries. Notebooks allow for "Living Post-Mortems." Because the queries are embedded directly into the document, the post-mortem can be revisited months later. A stakeholder can click on a chart within the report to see the live data as it exists now, providing an immediate sense of how the fix has held up over time.
III. Dynamic Runbooks
Perhaps the most significant implication for on-call efficiency is the transformation of static runbooks into dynamic, executable assets. Instead of a wiki page that tells an engineer what to look for, a Notebook can be linked directly to an alert. When the alert triggers, the engineer clicks the link to open a pre-populated Notebook that runs the necessary queries in real-time. This reduces the "on-call anxiety" that often accompanies paging into an unfamiliar service.
Looking Ahead: A New Standard for Observability
The move toward "narrative-driven observability" marks a departure from the dashboard-centric era of the last decade. As infrastructure becomes more ephemeral and distributed, the ability to document how a system is explored is becoming as important as the ability to see the system at all.
For teams currently struggling with the chaos of incident response, the call to action is clear. New Relic’s move to make this a core, free component of their platform suggests a strategic intent to standardize the way engineering teams document their work.
Getting Started:
To begin building your first notebook, log into your New Relic account. The platform’s interface allows for seamless migration of existing queries into the notebook format. By shifting from transient, chaotic activity to a persistent, collaborative process, engineering teams can ensure that every outage, every bug, and every performance spike contributes to the collective intelligence of the organization.
Disclaimer: The views expressed in this article are intended to provide an overview of the new product capabilities. For technical support, troubleshooting, or deep-dive questions regarding specific implementations, users are encouraged to visit the New Relic Explorers Hub at support.newrelic.com.
