New Relic Basics
APM & Monitoring magic
Dashboards & Alerts
NQRL &Data Nerd Stuff
Fun with Observability
100

This is the term for the overall system that collects, analyzes, and visualizes telemetry data in New Relic.

observability

100

This metric shows the average time it takes your app to respond to a request.

Response time

100

This feature lets you visualize data using custom queries and widgets.

dashboards

100

This is the query language used to retrieve and visualize data in New Relic.

NRQL (New Relic Query Language)

100

This is what your team feels when the alert noise is finally under control.

peace (or relief)? 😆

200

You’d visit this place to manage user permissions, API keys, and data ingest settings.

Account Settings page

200

This New Relic feature automatically detects unusual spikes or drops in metrics.

Anomaly detection

200

These notify you when metrics exceed certain thresholds.

Alerts

200

You can save and reuse your queries in dashboards using this type of chart component.

Data widget or chart panel

200

You probably need one of these after staring at a dashboard for 3 hours.

Coffee? Red Bull?

300

The main page where you can view all your connected services and applications.

Entity Explorer

300

This view helps you see the breakdown of response time by transaction type.

Transactions page

300

An alert condition that monitors a single metric or NRQL query is called this.

Policy condition

300

When analyzing latency, this NRQL function gives you a more resilient metric than AVERAGE() by focusing on the 95th or 99th part of a dataset.

PERCENTILE()

300

The act of diving deep into traces and logs just to find one small bug.

debugging (or observability spelunking)

400

This type of agent is installed in your application to collect performance metrics.

APM agent

400

You’d use this feature to trace the journey of a single request through your services.

distributed trace

400

You can use these visual elements to make dashboards easier to read at a glance.

Widgets or Visualizations

400

This NRQL function lets you count only one-of-a-kind values, such as distinct users or session IDs.

UNIQUES()

400

The magical trio of metrics you observe in any system: throughput, errors, and this.

Latency

500

This New Relic component provides a unified data platform for metrics, events, logs, and traces.

Telemetry Data Platform

500

This feature allows you to analyze service dependencies and latency between microservices.

Service Maps?

500

This alerting feature uses historical baselines to automatically adjust thresholds rather than relying on static values.

Dynamic Baseline Alerts 

500

This NRQL clause allows you to compare a metric’s current value to its past performance over a specific time window.

SINCE … COMPARE WITH

500

This observability “golden signal” measures how much work a system can handle per unit of time.

Throughput

M
e
n
u