In the high-stakes world of Site Reliability Engineering (SRE) and DevOps, the "2:00 AM incident" is a legendary rite of passage—and a persistent professional nightmare. When a production system begins to spiral, engineers are often thrust into a frantic, disjointed race against the clock. The current standard of observability—juggling dozens of browser tabs, manually stitching together screenshots, and attempting to explain ephemeral data patterns in static documents—has long been the primary bottleneck in incident resolution.
Today, New Relic is fundamentally changing this narrative with the general availability of New Relic Notebooks. Designed to serve as a persistent, collaborative, and narrative-driven workspace, the new feature aims to bring order to the chaos of troubleshooting, allowing engineers to treat data exploration as a structured, repeatable, and deeply connected process.
The Main Facts: What Are New Relic Notebooks?
At its core, New Relic Notebooks is a data exploration capability that integrates directly into the existing New Relic platform. It acts as a unified, multi-cell workspace where users can combine live telemetry queries, dynamic data visualizations, and rich markdown text into a single, cohesive document.
Unlike traditional dashboards, which provide static snapshots of health, or isolated query windows, which disappear the moment a tab is closed, Notebooks provide a living record of an investigation. They are designed for "Full Platform Users," ensuring that the capability is an extension of the existing ecosystem rather than a siloed tool. By allowing users to drill down sequentially, maintain time-bound context, and share findings with stakeholders without ever leaving the platform, New Relic is positioning Notebooks as the primary home for investigative work.
A Chronology of Chaos: The Evolution of Troubleshooting
To understand the necessity of this tool, one must examine the typical chronology of an incident under the "old" paradigm:
- The Trigger: At 2:00 AM, an alert fires. An on-call engineer wakes, logs into the platform, and opens a query window.
- The Tab Proliferation: The initial query reveals a spike in latency. The engineer opens a second tab to investigate specific service logs, a third to check database health, and a fourth to review recent deployment markers.
- The Context Gap: As the engineer jumps between tabs, the "mental map" of the incident begins to degrade. The time-bound context—the specific window where the anomaly occurred—is often lost or inconsistently applied across tabs.
- The Manual Handoff: Once the root cause is identified, the engineer is forced to take manual screenshots. These images are then pasted into a Confluence page, a Jira ticket, or a Slack channel.
- The Data Death: The moment the data is moved to a static document, it becomes "dead." It can no longer be interacted with, drilled into, or verified. If a team lead needs to see what happened five minutes before the spike, they cannot—they are limited to the pixels captured in the screenshot.
New Relic Notebooks effectively breaks this cycle. By replacing the static, fragmented document with a living, breathing workspace, the platform ensures that the "story" of the data remains intact from the first alert to the final post-mortem.
Supporting Data: Why Engineering Teams Need a New Approach
The industry is currently facing an epidemic of "context switching." According to recent developer productivity studies, engineers spend a significant portion of their time simply orienting themselves within data silos. The mental tax of re-establishing context after shifting from a logs window to a metrics dashboard is significant.
Notebooks solve this through three primary pillars:
- Logical Sequencing: Instead of juggling browser tabs, an engineer can build a logical "story" in a single document. Cell one can establish a high-level query; cell two filters by the specific service; cell three compares the anomalous latency against a historical baseline.
- Persistent Context: Because the Notebook saves the state, the time-bound parameters of the investigation are preserved. A senior engineer can pick up exactly where a junior engineer left off, without needing a verbal handover or a long, messy Slack transcript.
- Dynamic Interactivity: By using intelligent variables, results from one query can be piped into another. This allows for complex, multi-stage investigations that feel more like a programmed workflow than a manual search.
Implications for Modern SRE Practices
The introduction of Notebooks is poised to transform three key areas of the engineering lifecycle:
1. Accelerating Root-Cause Analysis (RCA)
By removing the friction of tab-switching, engineers can maintain a high-level flow state. The ability to compare live data side-by-side within a single document allows for rapid hypothesis testing. If an engineer suspects a database connection pool issue, they can immediately run a query to validate that specific metric directly below their service latency graph.
2. Living Post-Incident Reviews
Post-mortems are often dreaded because they require the manual assembly of evidence. With Notebooks, the "post-mortem" is written as the investigation happens. By embedding live queries and visualizations, stakeholders aren’t just reading a report—they are interacting with the incident data as it existed during the outage. This creates a higher level of transparency and accountability.
3. Dynamic Runbooks
Perhaps the most significant long-term impact is the shift from static runbooks to dynamic, executable assets. By linking a Notebook to an alert condition, an organization can provide its on-call engineers with a "guided experience." When an alert triggers, the engineer opens a pre-populated Notebook that contains the exact queries needed to diagnose that specific type of failure. This drastically lowers the "mean time to repair" (MTTR) for teams that are currently struggling with onboarding or complex microservice architectures.
Official Perspectives: Empowering the Engineer
Joanna Pacek, Senior Product Manager at New Relic, emphasizes that this tool was built with the direct needs of the modern practitioner in mind. "We wanted to shift data exploration from a transient, chaotic activity to a persistent, collaborative, and narrative-driven analytical process," Pacek notes.
Her vision is one where the tribal knowledge currently locked away in engineers’ heads—or lost in fragmented Slack messages—is captured in a reusable format. By empowering SREs and DevOps engineers to tell the "full story" of their data, New Relic is aiming to reduce the burnout associated with on-call shifts. When the tools are intuitive and the context is preserved, the pressure of the 2:00 AM incident becomes significantly more manageable.
The Path Forward: Integration and Community
The transition to using Notebooks is designed to be seamless. Because they are part of the core New Relic platform, there is no need for third-party integrations or external data pipelines. The platform is encouraging users to begin the process by migrating their most common incident investigation patterns into Notebooks.
For teams looking for support, New Relic has designated the Explorers Hub as the central venue for discourse. While the official documentation provides the technical scaffolding, the Explorers Hub allows for the exchange of "notebook templates," where users can share their own dynamic runbooks with the broader engineering community.
As the industry moves toward increasingly complex, distributed systems, the ability to maintain clarity amidst noise will be the defining trait of top-tier engineering organizations. New Relic Notebooks represents a clear step in that direction—moving beyond the static, the siloed, and the fragmented, toward a future where observability is as much about the narrative as it is about the metrics.
Log in to your New Relic account today to create your first Notebook and begin documenting your data’s story.
