Most Asked New Relic Interview Questions (2027)

40 most asked New Relic interview questions: NRQL, APM, OpenTelemetry, alerts, issues and workflows, service levels, cost control and scenarios.

Sep 25, 2025 - 15:26
Nov 8, 2026 - 01:33
 0  110
Most Asked New Relic Interview Questions (2027)

The most asked New Relic interview questions cover how telemetry gets in (APM agents, the infrastructure agent, Kubernetes integration and OpenTelemetry), how you query it with NRQL, how alerts are built from policies, conditions, issues and workflows, and how you use service levels, distributed tracing and logs in context during an incident. This page has 40 questions grouped by experience level.

If you are new to observability, read our 80+ New Relic interview questions for freshers first; it explains the basic terms. This page goes further into the questions interviewers ask most often once you have used New Relic at work. For how New Relic compares with other tools, see top observability tools for DevOps.

Key takeaways

  • Everything in New Relic is stored in its telemetry database and queried with NRQL. Being able to write NRQL live is the most tested skill.
  • Data arrives through New Relic agents, integrations and the OpenTelemetry Protocol (OTLP). Interviewers ask when you would choose each.
  • New Relic alerting is built from policies, conditions, alert events, issues, workflows and destinations, according to the New Relic alerts documentation.
  • Service levels turn SLIs into SLO tracking with error budgets, which is a common senior topic.
  • Cost and data volume control (sampling, drop rules, log filtering) comes up in almost every experienced round.

New Relic building blocks

CapabilityWhat it doesTypical interview angle
APM agentsInstrument application code (Java, .NET, Node.js, Python, Ruby, PHP, Go)Transactions, errors, throughput, traces
Infrastructure agentHost metrics, processes, on-host integrationsCapacity and host health
Kubernetes integrationCluster, node, pod and container dataPod restarts, resource limits
OpenTelemetryVendor-neutral traces, metrics and logs over OTLPAvoiding vendor lock-in
LogsLog ingestion and logs in contextLinking logs to traces
Browser, mobile, syntheticsReal user and scripted monitoringFront-end performance, uptime
NRQL and dashboardsQuery and visualise all dataWriting queries on the spot
Alerts and service levelsDetect problems and track SLOsNoise reduction, error budgets

Most asked questions for freshers

1. What is New Relic used for?

New Relic is an observability platform. It collects metrics, events, logs and traces from applications, hosts, containers, browsers and mobile apps, stores them in one database and lets you query, chart and alert on them.

2. What is an entity in New Relic?

An entity is anything that reports data or that New Relic can monitor: an application, host, Kubernetes cluster, browser app, synthetic monitor or service. Entities have a unique GUID and can be tagged and related to each other.

3. What is NRQL?

New Relic Query Language is an SQL-like language for querying New Relic data. You select from data types such as Transaction, Metric, Log or Span, filter with WHERE, group with FACET and chart over time with TIMESERIES.

SELECT average(duration), percentile(duration, 95)
FROM Transaction
WHERE appName = 'checkout-service'
FACET name
SINCE 1 hour ago
TIMESERIES

4. What are the golden signals and how do you see them in New Relic?

Latency, traffic, errors and saturation. APM shows response time, throughput and error rate for each service, and infrastructure data shows CPU, memory and disk saturation.

5. What does an APM agent collect?

Transactions (web requests and background jobs), their duration and breakdown into database, external and code segments, errors with stack traces, and distributed tracing spans. You install it as a library or package in the application runtime and give it a license key and app name.

6. What is Apdex?

Apdex scores user satisfaction from 0 to 1 based on a response time threshold T: requests faster than T are satisfied, up to 4T are tolerating, slower ones and errors are frustrated. New Relic shows Apdex for APM and browser applications.

7. What is distributed tracing?

Distributed tracing follows a request across services. Each service adds spans with timing, linked by a shared trace ID passed in headers (W3C Trace Context). In New Relic you open a trace to see which service or call made the request slow.

8. What is synthetic monitoring?

Scheduled checks that run from New Relic locations or private locations: simple pings, scripted browser journeys and API tests. They tell you a site is down even when no real users are active.

9. What is the difference between browser monitoring and APM?

APM measures server-side work. Browser monitoring measures what users experience in the page: page load, Core Web Vitals, JavaScript errors and AJAX calls. Together they show whether slowness is in the front end or the back end.

10. How do you add tags to entities and why?

Through agent configuration, the UI or the API. Tags such as team, env and service let you filter dashboards, scope alerts and find owners quickly.

Questions for 2 to 5 years of experience

11. How do you send OpenTelemetry data to New Relic?

Export it over OTLP to New Relic's OTLP endpoint with your license key in the api-key header, either directly from the SDK or through an OpenTelemetry Collector. Use the Collector when you want batching, filtering or to send data to more than one backend.

12. When would you choose a New Relic agent over OpenTelemetry?

Agents give the deepest out-of-the-box instrumentation and New Relic-specific features with little setup. OpenTelemetry keeps instrumentation vendor neutral and suits teams standardising across tools. Many companies run both: agents on older services and OpenTelemetry on new ones.

13. How do you monitor Kubernetes with New Relic?

Install the Kubernetes integration, usually with the Helm chart, which deploys the infrastructure agent and supporting components. It reports cluster, node, pod and container metrics and Kubernetes events, and can link pods to the APM services running in them.

14. Write an NRQL query for error rate by service over the last day.

SELECT percentage(count(*), WHERE error IS true)
FROM Transaction
FACET appName
SINCE 1 day ago

Using percentage() with a WHERE clause gives a ratio rather than a raw count, which is what an error rate alert should use.

15. How do you compare this week's latency with last week's?

Add COMPARE WITH 1 week ago to a TIMESERIES query. It overlays the earlier period so you can spot regressions after a release.

16. How is a New Relic alert built?

A policy groups conditions. A condition applies thresholds to a signal, often an NRQL query. When a threshold is breached, an alert event is created; related alert events are grouped into an issue, and workflows decide when and where issues are sent through destinations such as Slack, PagerDuty, email or webhooks.

17. What NRQL alert condition settings matter most?

The query, the threshold and how long it must be breached, the aggregation window and method, and how to treat signal loss (for example opening an alert when data stops). Wrong aggregation settings are a common cause of late or missing alerts.

18. What is a baseline or anomaly condition?

Instead of a fixed threshold, the condition learns the normal pattern of a signal and alerts when it moves outside the expected range. It suits metrics with daily or weekly cycles, such as traffic.

19. How do you reduce alert noise?

Alert on user-facing symptoms like error rate and latency rather than every host metric, use sensible durations, group related alerts into issues, route by team with workflows, and review alerts nobody acts on.

20. What are logs in context?

Agents add trace and span IDs to log lines so New Relic can show the logs for a specific trace or error. It removes the step of searching logs by timestamp during an incident.

21. How do you track deployments?

Record change events (deployments) through the API or CI integrations. New Relic marks them on charts, so you can see whether a release caused a change in errors or latency.

22. What is the errors inbox?

A view that groups errors across APM, browser and mobile into error groups, which you can assign, resolve or ignore. It works like a triage queue for application errors.

23. How do you build a dashboard teams actually use?

Start from questions the team asks during incidents, put service-level indicators at the top, use template variables for environment and service, and keep each widget to one NRQL query with a clear title.

24. How do you automate New Relic configuration?

Use the New Relic Terraform provider for alert policies, conditions, workflows, dashboards and synthetics, or call NerdGraph, New Relic's GraphQL API, from scripts. Keep the code in Git and apply it through CI.

25. How do you monitor a third-party API your app depends on?

APM shows external call timing and errors per host. Add a synthetic API test against the dependency and an alert on its error rate or latency so you know whether a slowdown is yours or theirs.

Senior New Relic questions

26. How do you define service levels in New Relic?

Create a service level on an entity with an SLI defined as valid events and good events (for example requests faster than 500 ms that did not error), set an SLO target and period, and track the error budget. Alert on fast budget burn rather than single threshold breaches.

27. How do you control New Relic costs?

Measure ingest by source with NRQL on usage data, drop data you never query with drop rules, filter noisy logs at the source or in the Collector, sample traces where volume is high, and review who needs full platform user access. Do not guess prices in an interview; say you would check the current pricing page.

28. How do you roll out New Relic across 200 services?

Standardise agent configuration and naming (service, environment, team tags), bake agents into base images or use Kubernetes auto-instrumentation where available, create a default dashboard and alert set per service through Terraform, and give each team ownership of its alerts.

29. How do you handle sensitive data in telemetry?

Configure agents to avoid capturing request parameters and SQL values, obfuscate log attributes, apply drop or obfuscation rules before storage, and limit access with roles. Check compliance needs such as data region and retention with your security team.

30. How do you design alerts for a microservices platform?

Each service alerts on its own SLO burn and golden signals and routes to its team. Platform alerts cover shared components such as Kubernetes nodes, databases and queues. Use entity relationships and service maps to see upstream causes during an incident.

31. How do you integrate New Relic into incident response?

Send issues to the paging tool through workflows, include links to the relevant dashboard and runbook in the notification, use deployment markers and traces to find the cause, and add a post-incident step to fix gaps in monitoring.

32. How do you manage access for many teams?

Use SSO with SCIM provisioning, assign user types according to need, group users and give roles scoped to the accounts they work in, and separate production and non-production accounts where that helps control access.

33. How would you migrate from another monitoring tool to New Relic?

Inventory existing dashboards and alerts, decide which still matter, instrument services (OpenTelemetry makes later changes easier), rebuild key alerts first, run both tools in parallel for a few release cycles and then retire the old one.

34. How do you prove observability is improving?

Track mean time to detect and resolve incidents, the share of incidents found by alerts rather than customers, SLO attainment and the number of noisy alerts removed. Our post on observability and SLOs explains the link.

Scenario questions

35. Response time doubled after a release. How do you find the cause in New Relic?

Check the deployment marker on the APM chart, compare transaction breakdowns before and after, open slow traces to find the span that grew (often a database query or external call), and confirm with logs in context. Roll back if the impact is serious, then fix.

36. An alert should have fired during an outage but did not. What do you check?

Whether data kept arriving (signal loss settings), the aggregation window and delay, whether the threshold duration was longer than the outage, and whether a workflow filter dropped the issue. Test the condition with a past time range.

37. An APM app stopped reporting after a deployment. What do you do?

Check the agent log on the host or container, confirm the license key and app name environment variables are still set, check that outbound network access to New Relic is allowed, and verify the agent version supports the new runtime version.

38. Log ingest suddenly tripled. How do you respond?

Query logs by source and attribute to find the noisy service, ask the owning team to fix the logging level, add a drop rule or Collector filter as a short-term fix, and add an alert on ingest volume.

39. Users in one region report a slow site while APM looks fine. Where do you look?

Browser monitoring by geography, synthetic checks from locations in that region and CDN or DNS performance. The problem is often outside the application servers.

40. Pods in a cluster keep restarting. How does New Relic help?

The Kubernetes integration shows restart counts, container status and events such as OOMKilled. Compare memory use with limits, link to the APM service for errors at the same time, and alert on restart rate.

How to prepare

Create a free New Relic account, install an APM agent on a small app and the Kubernetes integration on a local cluster, then practise NRQL: averages, percentiles, FACET, TIMESERIES and COMPARE WITH. Build one alert condition and one workflow end to end. Our DevOps training in Pune covers monitoring in CI/CD and Kubernetes, and the Prometheus and Grafana course covers open source observability skills that carry over. For more topics, use the 200+ DevOps interview questions guide and 10 monitoring alerts every DevOps engineer should configure.

Frequently asked questions

What is the most important New Relic skill for interviews?

Writing NRQL. Most dashboards, alert conditions and investigations depend on it, and interviewers often ask you to write a query on the spot.

Does New Relic support OpenTelemetry?

Yes. You can send traces, metrics and logs to New Relic over OTLP, directly or through an OpenTelemetry Collector.

How are alerts organised in New Relic?

Policies hold conditions. Breached conditions create alert events, which are grouped into issues, and workflows send issues to destinations such as Slack or PagerDuty.

What is the difference between APM and infrastructure monitoring?

APM measures application code: transactions, errors and traces. Infrastructure monitoring measures hosts, containers and their resources.

How do you track SLOs in New Relic?

Create service levels with an SLI based on good and valid events, set an SLO target and monitor the error budget.

Can New Relic configuration be managed as code?

Yes. The New Relic Terraform provider and the NerdGraph API let you manage alerts, dashboards and synthetics from Git.

Official references

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Mridul I am a passionate technology enthusiast with a strong focus on DevOps, Cloud Computing, and Cybersecurity. Through my blogs at DevOps Training Institute, I aim to simplify complex concepts and share practical insights for learners and professionals. My goal is to empower readers with knowledge, hands-on tips, and industry best practices to stay ahead in the ever-evolving world of DevOps.