Scenario-Based New Relic Interview Questions (2027)

30 scenario-based New Relic interview questions with NRQL: missing APM data, noisy alerts, broken traces, ingest spikes, Kubernetes and OpenTelemetry.

Sep 25, 2025 - 16:03
Nov 6, 2026 - 15:02
 0  93
Scenario-Based New Relic Interview Questions (2027)

Scenario-based New Relic interview questions describe a production situation, such as missing APM data, a noisy alert, a slow endpoint, broken distributed traces or a sudden jump in ingest, and ask how you would investigate it in New Relic. Strong answers name the data type to query, show the NRQL, and end with a fix and a prevention step.

This page has 30 scenario questions with worked answers, grouped by experience level. If you need definitions first, start with the 80+ New Relic interview questions for freshers, then the most asked New Relic interview questions, which is the main question bank. Terms and alert settings below were checked against New Relic documentation in November 2026.

Key takeaways

  • Answer every scenario in four parts: what you see, what you query, what you change, how you stop it happening again.
  • Know the core event types you will query: Transaction, TransactionError, Span, Log, SystemSample, K8sContainerSample and NrIntegrationError.
  • New Relic alerting uses policies, conditions, alert events grouped into issues, and workflows that send notifications to destinations.
  • Streaming alert settings matter in scenarios: aggregation method (event flow, event timer, cadence), aggregation window, delay, loss of signal and gap filling.
  • Missing data questions usually come down to the key, the app name, network egress, the agent version or an ingest limit, and NrIntegrationError tells you which.

A four-step answer frame

StepWhat to sayExample
ObserveThe symptom and its scopep95 latency on /checkout doubled in one region
QueryThe event type and NRQLFROM Transaction SELECT percentile(duration, 95) FACET name TIMESERIES
FixThe change and how you confirm itRoll back the deploy, watch the chart recover
PreventAlert, test or process changeAdd a latency service level and a change-tracking marker in CI

Scenarios for freshers (1 to 10)

1. A new Java service is deployed with the APM agent, but nothing appears in New Relic. What do you check?

Check the agent log first. Confirm the license key is set (in newrelic.yml or the NEW_RELIC_LICENSE_KEY environment variable), the app name is set, the agent jar is passed with -javaagent, and the host can reach New Relic's endpoints on port 443 (EU accounts use EU endpoints). Then query NrIntegrationError for rejected data.

SELECT count(*) FROM NrIntegrationError
FACET category, message SINCE 1 hour ago

2. Two environments report into the same APM entity and the data is mixed. Fix it.

Give each environment a distinct app name (for example checkout-prod and checkout-staging) or separate accounts, and add an environment tag. Mixed data makes alerts and baselines unreliable, so fix it before tuning anything else.

3. A manager asks for the slowest endpoints in the last day. How do you answer?

SELECT average(duration), percentile(duration, 95), count(*)
FROM Transaction WHERE appName = 'checkout-prod'
FACET name SINCE 1 day ago LIMIT 10

Sort by p95 rather than the average, because averages hide slow outliers. Include the count so a rarely called slow endpoint is not mistaken for the main problem.

4. Users report errors, but the APM error rate looks normal. Why might that be?

The errors may happen before requests reach the app (load balancer, CDN or DNS), in the browser, or be handled exceptions the agent does not count as errors. Check browser monitoring (JavaScriptError, PageView), synthetic monitors, and logs from the load balancer. Configure expected and ignored errors correctly in the agent.

5. How do you find errors for one endpoint with their messages?

SELECT count(*) FROM TransactionError
WHERE transactionName LIKE '%checkout%'
FACET error.class, error.message SINCE 3 hours ago

Then open Errors Inbox to see grouped errors with stack traces and assign them to an owner.

6. A host disappears from the infrastructure list. What happened?

The infrastructure agent stopped reporting: the host shut down, the agent service stopped, the network path is blocked, or the license key changed. Check the agent service status and logs on the host. Use a loss-of-signal setting on a host alert condition so you are told when data stops.

7. How do you check logs for the same request you see in a trace?

Turn on logs in context in the APM agent so log lines carry trace and span IDs. Then you can open the trace and jump to its logs, or query Log by trace.id.

8. A dashboard chart shows a gap. Is the service down?

Not necessarily. A gap means no data arrived for that query. Check whether traffic was zero (an idle service), the agent stopped, or the query filter changed. Compare with an infrastructure metric for the same host or pod.

9. How do you monitor a public website from outside your network?

Create synthetic monitors from several public locations: a ping or simple browser monitor for availability, a scripted browser monitor for a login or checkout path, and a certificate check monitor for TLS expiry. Alert on failures from more than one location to avoid false alarms.

10. How do you show a deploy on New Relic charts?

Record the deployment with change tracking, from your CI pipeline through NerdGraph or a supported integration. Charts and the entity's change view then show a marker, so you can link a regression to a release.

Scenarios for 2 to 5 years of experience (11 to 22)

11. An alert fires every night at 2 a.m. and closes on its own. How do you fix it?

Find the cause in the alert event history and the signal: often a batch job, a backup or a low-traffic window where a few errors make a big percentage. Options are to require a minimum request count in the NRQL, use a longer threshold duration, use an anomaly (baseline) condition, or add a muting rule for a planned window. Do not just raise the threshold until it stops firing.

SELECT percentage(count(*), WHERE error IS true)
FROM Transaction WHERE appName = 'checkout-prod'

12. An alert on a batch job never fires even when the job fails. Why?

Batch data arrives in bursts, and with the default event flow aggregation the windows may not close as expected. Event timer aggregation suits infrequent or batched data. Also add a loss-of-signal setting so a job that stops sending data opens an alert event.

13. A team wants alerts only in Slack for warnings and PagerDuty for critical. How do you set it up?

Set warning and critical thresholds on the conditions, then create workflows that filter issues by priority and send to different destinations: Slack for warnings, PagerDuty for critical. Test each workflow with a test notification.

14. Distributed traces stop at one service and do not show the downstream calls. What is wrong?

Trace context is not being passed across that hop. Check that the agents on both sides have distributed tracing enabled, that a proxy or message queue is not stripping the traceparent header, and that services instrumented with OpenTelemetry and New Relic agents both use W3C Trace Context. For async messaging, check that the library is supported or add manual instrumentation.

15. Ingest for logs doubled overnight. How do you find the source and control it?

SELECT bytecountestimate()/10e8 AS 'GB'
FROM Log FACET service.name, level SINCE 1 day ago

Find the service and log level that grew, usually debug logging left on after an incident. Fix the logging level at the source, and use drop rules or log parsing rules to discard low-value data at ingest. Add an alert on ingest volume so the next spike is caught in hours, not at the end of the month.

16. Pod restarts are rising in a Kubernetes cluster. How do you investigate in New Relic?

SELECT max(restartCount) FROM K8sContainerSample
WHERE clusterName = 'prod' FACET podName, containerName
SINCE 6 hours ago

Check whether restarts follow memory limits (OOM kills), failing liveness probes or crashes after a deploy. Compare memory use with limits in the same sample, and look at the pod's logs and Kubernetes events.

17. A service's p95 latency rose after a release, but CPU and memory look fine. Next step?

Open the slow transactions and their traces. Look at the breakdown by segment: database queries, external calls or time in a specific function. A new N+1 query pattern or a slower downstream API are common causes. Confirm with a query faceted by the external host or database operation.

18. How do you define SLOs in New Relic for a checkout service?

Use service level management to create SLIs, such as the share of successful checkout transactions and the share under a latency threshold, with targets and a time window. New Relic then shows compliance and remaining error budget, and you can alert on burn rate. See our error budget guide for the reasoning.

19. You inherit 400 alert conditions and on-call engineers ignore most pages. What do you do?

Pull the alert event history and rank conditions by how often they fire and whether anyone acted. Delete or downgrade conditions that never led to action, merge duplicates, move cause-based alerts to dashboards, and keep pages for symptoms with runbooks. Review the list again after a month.

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

Point the OpenTelemetry SDK or Collector OTLP exporter at New Relic's OTLP endpoint for your region and add the license key as the api-key header. Keep resource attributes such as service.name consistent so entities are created correctly.

exporters:
  otlphttp:
    endpoint: https://otlp.nr-data.net
    headers:
      api-key: ${env:NEW_RELIC_LICENSE_KEY}

21. A browser page is slow for real users but fast in your tests. How do you check?

Use browser monitoring data, which reflects real devices and networks. Facet page load time and Core Web Vitals by country, device type and browser. Your test machine is often a fast desktop on a fast network, so the problem may be a large script bundle on mobile.

22. How would you manage New Relic alerts and dashboards as code?

Use the New Relic Terraform provider to define policies, NRQL conditions, workflows and dashboards in Git, reviewed through pull requests. This keeps settings consistent across environments and lets you roll back a bad change. Our infrastructure as code tools guide compares options.

Scenarios for senior engineers (23 to 30)

23. Leadership asks you to cut the New Relic bill without losing visibility. Plan?

Measure ingest by source and data type, then cut what nobody uses: debug logs, duplicate metrics, high-cardinality attributes and low-value environments. Apply sampling where it is safe, use drop rules, and set retention to what teams actually query. Report the change in ingest and confirm key dashboards and alerts still work.

24. During a major incident, three teams each blame another service. How do you use New Relic to settle it?

Open the service map and distributed traces for failing requests and find where errors or latency start. Compare error rates for each service on one chart with the same time window, and check change tracking for deploys near the start time. Share the trace and chart in the incident channel so the discussion moves to evidence.

25. How do you design alerting for 200 microservices without writing 200 sets of conditions by hand?

Write NRQL conditions that facet by service, use tags to scope them, and generate per-team policies with Terraform modules. Base the main pages on service levels and golden signals, with team-specific conditions added only where needed.

26. A database looks slow in APM but the DBA says the database is fine. How do you investigate?

Check whether time is spent in the query or waiting for a connection. Connection pool exhaustion in the app shows as slow database segments while the database is idle. Compare query time in traces with database-side metrics from the database integration, and check pool size against concurrency.

27. Security asks whether any service uses a vulnerable library version. Can New Relic help?

Yes. APM agents report the libraries a service loads, and New Relic's vulnerability management can list known vulnerabilities by entity. Use it alongside your existing dependency scanning in CI, not as a replacement.

28. How do you roll out a new agent version across hundreds of services safely?

Pin agent versions in build files or base images, upgrade a few low-risk services first, watch overhead and data shape for a few days, then upgrade in waves. Read the agent release notes for breaking changes, and keep a quick path to the previous version.

29. Your company runs both New Relic and Prometheus. How do you avoid two sources of truth?

Decide which tool owns which signal and alert. You can send Prometheus metrics to New Relic through remote write or the Prometheus integrations, so dashboards and alerts sit in one place. Document the owner for each alert so one incident does not page twice.

30. How do you show that observability work improved reliability?

Track MTTD, MTTR, the number of pages per on-call week and SLO compliance before and after the change. Pair the numbers with a few postmortems showing faster detection. Our observability tools guide and scenario-based SRE questions go further on measuring reliability.

Event types to know for scenario rounds

Event typeSourceTypical scenario
TransactionAPM agentsSlow or failing endpoints
TransactionErrorAPM agentsError details and messages
SpanDistributed tracingBroken or slow traces
LogLog forwarding, logs in contextIngest spikes, request debugging
SystemSampleInfrastructure agentHost CPU, memory, disk
K8sContainerSampleKubernetes integrationRestarts, limits, OOM kills
PageView, JavaScriptErrorBrowser monitoringReal user slowness and errors
NrIntegrationErrorNew Relic platformMissing or rejected data

How to practise

New Relic offers a free tier, which is enough to instrument a small app, break it on purpose and write the NRQL for each scenario above. Pair it with open source tools so you can explain the concepts beyond one vendor; our Prometheus and Grafana training and DevOps training (Kharadi, Pune classroom and live online) cover monitoring, alerting and incident response hands-on. For general rounds, use the 200+ DevOps interview questions guide.

Frequently asked questions

What are scenario-based New Relic interview questions?

They describe a production problem, such as missing data, noisy alerts or slow endpoints, and ask how you would investigate and fix it using New Relic. Interviewers look for the right data type, a working NRQL query and a prevention step.

Why is my New Relic APM agent not reporting data?

Common causes are a missing or wrong license key, a missing app name, blocked outbound traffic on port 443, the agent not being loaded, or an unsupported version. Check the agent log and query NrIntegrationError for rejected data.

How do I reduce noisy New Relic alerts?

Review alert event history, require a minimum request count in percentage conditions, lengthen threshold durations, use anomaly conditions for seasonal traffic, and mute planned windows. Remove alerts that never lead to action.

Which aggregation method should I use for batch job alerts?

New Relic documents event timer aggregation as suited to infrequent or batched data, while event flow suits steady data. Add a loss-of-signal setting so you are alerted when the job stops sending data.

How do I find what is driving New Relic ingest costs?

Query bytecountestimate() faceted by data type, service and log level to find the largest sources. Then lower log levels, drop unused attributes with drop rules and set sampling where it is safe.

Can New Relic receive OpenTelemetry data?

Yes. Configure the OpenTelemetry SDK or Collector OTLP exporter to send to New Relic's OTLP endpoint for your region, with the license key in the api-key header.

Which New Relic interview guide should I read first?

Start with the 80+ questions for freshers guide for definitions, then the most asked questions guide. Use this scenario page last, once you are comfortable with NRQL and alerting terms.

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.