developmentContext + New Relic
Transform New Relic observability intelligence into searchable operational knowledge with an enterprise-grade knowledge graph
OVERVIEW
New Relic is the full-stack observability platform where engineering teams instrument, measure, and understand their systems -- through APM traces that reveal application performance, infrastructure agents that monitor host and container health, and NRQL dashboards that encode the operational queries teams use to assess system state. Over time, New Relic accumulates a deep repository of operational intelligence: the alert policies that define what constitutes degraded service, the custom dashboards that reflect how teams reason about system behavior, the workload definitions that group related entities, and the incident records that capture how engineers diagnosed and resolved production issues. But this knowledge remains locked within New Relic's interface, disconnected from the Jira tickets tracking performance improvements, the Confluence capacity planning documents, and the GitHub commits that changed application behavior.
Context connects to your New Relic account and extracts the organizational knowledge embedded in alert policies, NRQL dashboard definitions, workload configurations, incident records, and entity metadata. Using permission-aware indexing that respects your New Relic account-level and role-based access controls, Context builds a knowledge graph that maps relationships between services, alert conditions, dashboards, engineers, and the broader context from your entire tool stack.
Unlike cloud-based search tools that require your observability metadata to be processed on external infrastructure, Context deploys entirely on your network -- on-premise, in your VPC, or in air-gapped environments. Your alert policy configurations, custom NRQL queries, and incident investigation records never leave your control. For defense organizations monitoring classified system telemetry, aerospace companies tracking mission-critical avionics software, and financial institutions observing high-frequency trading platforms, observability data reveals system architecture, performance envelopes, and failure boundaries. Context ensures this intelligence remains within your security boundary while making it searchable and actionable. Every answer is backed by citations to specific New Relic entities, dashboards, or alert policies, maintaining full traceability.
KEY CAPABILITIES
Key Capabilities
- 01Permission-aware indexing of New Relic alert policies, NRQL dashboards, workloads, and incident records that respects account-level and role-based access controls
- 02Alert policy intent extraction that captures not just condition thresholds but the operational reasoning behind NRQL queries, evaluation windows, and notification channels
- 03NRQL dashboard knowledge preservation that indexes custom query logic, widget configurations, and filter patterns so institutional observability expertise is never lost when team members leave
- 04Entity relationship mapping that builds a searchable graph connecting New Relic entities to their alert conditions, dashboards, owning teams, and related infrastructure components
- 05Cross-tool performance correlation that links New Relic APM data to related GitHub deployments, Jira performance tickets, PagerDuty escalation policies, and Confluence architecture documentation automatically
USE CASES
Use Cases
Operational Knowledge Preservation During Team Transitions
When senior engineers leave or teams reorganize, critical observability knowledge often vanishes -- why specific NRQL alert conditions use particular thresholds, which dashboard panels are essential during incident triage, and what workload groupings reflect about service dependencies. Context preserves this intelligence by indexing New Relic configurations alongside the Jira tickets that motivated them, the Confluence documents that explain architectural decisions, and the Slack conversations where engineers discussed monitoring strategy. New team members can ask "why is the API gateway latency alert set to 500ms?" and receive the full decision history.
Cross-Platform Incident Correlation for Classified Systems
Defense and intelligence organizations often operate multiple isolated New Relic accounts across different classification levels or programs. Context indexes each account's observability knowledge within the appropriate security boundary, enabling engineers to search across alert histories, dashboard definitions, and incident records without crossing classification boundaries. When a similar performance pattern appears across programs, Context surfaces the relevant historical context from each account independently, respecting compartmentalization requirements.
Infrastructure Migration Impact Analysis
Before migrating workloads to new infrastructure -- whether moving between cloud regions, transitioning to Kubernetes, or consolidating data centers -- teams need to understand what observability coverage exists. Context answers questions like "what New Relic alert policies reference the us-east-1 infrastructure?" or "which dashboards track performance for services running on the legacy VM fleet?" by querying the knowledge graph built from New Relic entity metadata, alert conditions, and dashboard NRQL queries -- connected to the broader migration context in Jira and Confluence.
Compliance Audit and Monitoring Governance
Regulated industries require evidence that critical systems are adequately monitored. Context maps New Relic alert policies, SLI/SLO configurations, and workload definitions into a searchable knowledge graph that auditors and compliance officers can query. Questions like "what monitoring coverage exists for PCI-scoped services?" or "which production databases have alerting configured for availability?" return citation-backed answers referencing specific New Relic configurations, the teams responsible, and the compliance requirements documented in Jira and Confluence.
HOW IT WORKS
How It Works
DATA FLOW
SECURITY & COMPLIANCE
Security & Compliance
SOC 2 Type II
GDPR
HIPAA
ISO 27001DEPLOYMENT
Deployment Options
DEPLOYMENT ARCHITECTURE
FREQUENTLY ASKED QUESTIONS
Frequently Asked Questions
How does Context connect to New Relic?
Context integrates with New Relic through the NerdGraph GraphQL API using a dedicated user API key with read-only permissions. Once configured, Context indexes alert policies, dashboards, workloads, entity metadata, and incident records. The connection is read-only -- Context never modifies your New Relic configurations, alert policies, or dashboards. All indexing and processing happens on your infrastructure, whether deployed on-premise, in your VPC, or in an air-gapped environment.
Does Context index raw New Relic metric or trace data?
No. Context focuses on the knowledge artifacts in New Relic -- alert policy definitions, NRQL dashboard queries, workload configurations, entity relationships, and incident records -- rather than raw metric streams or individual trace spans. This approach captures the operational intelligence your engineering team has encoded in New Relic, making monitoring decisions and observability patterns searchable. Raw telemetry data remains in New Relic and is referenced through citations when relevant.
Can Context work with New Relic in classified environments?
Yes. Context deploys entirely on your infrastructure with no external data processing dependencies. For organizations operating under ITAR, FedRAMP, CMMC, or SOC 2 requirements, Context ensures that indexed observability knowledge -- including NRQL queries that reveal system architecture and alert conditions that expose performance boundaries -- never leaves your controlled environment. The on-premise deployment model supports air-gapped networks where New Relic is self-hosted or operated on isolated infrastructure.
How does Context handle multi-account New Relic setups?
Context supports New Relic's multi-account model, indexing knowledge artifacts from each account while maintaining account-level access boundaries. Users only see results from New Relic accounts they have access to. This is particularly important for defense organizations that use separate New Relic accounts for different classification levels or program compartments -- each account's observability knowledge is indexed and searched independently within the appropriate security boundary.
Can Context link New Relic data to incident response workflows?
Yes. Context's knowledge graph automatically links New Relic artifacts to related content across connected tools. An alert policy is linked to its PagerDuty notification channel, the Slack channel where on-call engineers are notified, the Jira tickets tracking performance improvements, and the Confluence runbooks documenting response procedures. When an incident occurs, engineers can search for the full context spanning New Relic observability data, communication history, and documentation.
SETUP OVERVIEW
Setup Overview
Connecting New Relic to Context requires New Relic account administrator access and typically takes around 20 minutes. The process involves generating a dedicated user API key with read-only NerdGraph permissions, selecting which New Relic accounts to index, and mapping New Relic roles to Context access controls. Context handles the rest -- indexing begins automatically and the knowledge graph starts building within minutes. No changes to your New Relic instrumentation, alert policies, or engineering workflows are required.
RELATED INTEGRATIONS
Related Integrations
Datadog
Connect Context to Datadog to extract operational knowledge from monitors, dashboards, and incident investigations. On-premise deployment with permission-aware indexing.
PagerDuty
Connect Context to PagerDuty to extract incident response knowledge from alerts, escalation policies, and post-incident reviews. On-premise deployment with permission-aware indexing.
Splunk
Connect Context to Splunk to surface security intelligence and operational insights from log data, security events, and analytics dashboards. On-premise deployment with permission-aware indexing.
Jira
Connect Context to Jira to transform tickets, epics, and project history into connected organizational knowledge. Permission-aware indexing with on-premise deployment.
Slack
Connect Context to Slack to surface organizational knowledge buried in conversations, threads, and channels. Permission-aware indexing with on-premise deployment.
Ready to connect New Relic?
See Context + New Relic in action with a 30-minute technical walkthrough tailored to your environment.
BOOK A DEMO