New Relic Verified Foundation key terms

A monitored object such as a host, application, service, or browser app that New Relic tracks as a single unit with its own attributes, alerts, and health status.

The four core health indicators - latency, traffic, errors, and saturation - that summarize how well a service is performing and are surfaced on entity overview pages.

A satisfaction score from 0 to 1 that compares response times against a target threshold T, classifying requests as satisfied, tolerating, or frustrated.

A single logical unit of work handled by an application, such as a web request or background job, which New Relic times and traces end to end.

A detailed breakdown of one slow transaction showing each segment and its duration, used to pinpoint which method or external call caused the delay.

A method of following a single request across multiple services by propagating a trace identifier, letting you see each service's span and where time is spent.

A timed operation within a distributed trace representing work done by one service or component, with a start time, duration, and parent-child relationships.

Language-specific software installed in an application that instruments code, collects telemetry, and reports it to New Relic without requiring code changes in most cases.

Real user monitoring that injects a JavaScript agent into web pages to measure page load timing, AJAX calls, and JavaScript errors experienced by actual visitors.

Scripted checks that run from managed locations on a schedule to test availability and performance of endpoints, simulating user journeys from outside your network.

Google-defined user experience metrics - Largest Contentful Paint, Interaction to Next Paint, and Cumulative Layout Shift - that browser monitoring reports for real page loads.

A period of user activity in a browser or mobile app, grouping page views and interactions so you can analyze behavior and performance per visit.

A privacy-conscious recording of on-screen interactions during a user session, letting you watch what a visitor saw when an error or slowdown occurred.

New Relic's set of machine-learning capabilities that detect anomalies, correlate incidents, and reduce alert noise by grouping related problems automatically.

Automatic identification of metric behavior that deviates from a learned baseline, triggering alerts when values fall outside expected dynamic bounds.

A container that groups alert conditions and defines incident creation preferences, such as rollup strategy, for a set of monitored entities.

A rule specifying which metric or event to evaluate, the threshold and duration that must be breached, and the policy it reports into.

An alert condition whose threshold is expressed as a NRQL query, enabling alerts on aggregated or filtered event data rather than a single static metric.

A saved grouping of entities that can be viewed and alerted on together, useful for tracking a business service composed of many underlying components.

A monitored server or virtual machine reporting CPU, memory, disk, and network metrics through an infrastructure agent, forming the base entity for infrastructure monitoring.

Lightweight software installed on a host that collects system metrics and forwards logs and events to New Relic for infrastructure monitoring.

A polling integration that pulls metrics and inventory from a cloud provider such as AWS, Azure, or GCP into New Relic using read-only credentials.

A cluster-level integration that collects metrics and events about nodes, pods, deployments, and control-plane components for container observability.

A component that tails log files or receives log streams on a host and ships them to New Relic, optionally enriching them with attributes and parsing rules.

A configuration that extracts structured attributes from raw log messages using patterns such as Grok, making log data filterable and queryable in NRQL.

New Relic Query Language, a SQL-like syntax for selecting, filtering, and aggregating telemetry events, used in dashboards, alerts, and ad hoc queries.

A single record of telemetry - such as a transaction, log line, or metric sample - stored with a type name and attributes that NRQL queries operate on.

A key-value pair attached to an event or entity that provides context, such as host name, HTTP status, or custom tags, and can be used to filter queries.

A key-value label applied to entities for organization, filtering, and scoping alerts or access, distinct from attributes attached to individual telemetry events.

A shareable collection of charts, tables, and NRQL queries arranged in a layout to visualize the health and performance of monitored systems.

A record created when alert conditions breach their thresholds, grouping related violations and tracking acknowledgement, resolution, and notification history.

A target for a reliability metric, such as 99.9 percent successful requests over 30 days, with an error budget tracked against monitored events.

A unique identifier assigned to a distributed request that links spans across services so a full end-to-end trace can be reconstructed.

The process of receiving telemetry from agents, integrations, and APIs into New Relic, which is the basis for usage-based billing on most account tiers.

The period for which ingested telemetry remains queryable, varying by data type and account tier, after which it is no longer available in the platform.

A named user granted access to the account, with permissions determined by role; seat count and access level depend on the subscription tier.

A subscription level - such as free, standard, or enterprise - that determines included data volume, retention, support, and feature access.