Turn on New Relic Distributed Tracing for a Spring Boot App and Spot Latency Hotspots
Discover how to enable New Relic Distributed Tracing in a Spring Boot app, spot latency hotspots, and understand the overhead costs.
Loading…
ReadMeFeed / Community knowledge
#new-relic
Real questions. Useful conversations. Find the people who know your stack.
newrelicEnable and Verify Distributed Tracing in New Relic for Microservices
Learn how to get end‑to‑end visibility across microservices with New Relic’s Distributed Tracing. The guide covers automatic header injection, custom span creation, sampling, and common pitfalls such as broken traces in async queues.
Enabling New Relic Distributed Tracing in Java Microservices: Setup, Trade‑offs, and Verification
Enable New Relic Distributed Tracing for Java microservices quickly: set the agent flag, tune sampling, verify in UI/NRQL, and understand the performance trade‑offs. Follow our step‑by‑step guide to see end‑to‑end request paths and root‑cause latency hotspots.
New Relic Synthetics: When a Scripted Browser Monitor Beats an API Test
A decision guide for choosing between New Relic Synthetics Scripted Browser and API Test monitors: shared constraints, what each can assert, and how to validate a monitor before trusting it.
Integrating the New Relic Java APM Agent into Spring Boot: A Step‑by‑Step Task Guide
Attach the New Relic Java agent to a Spring Boot app, configure via newrelic.yml or env vars, validate metrics in New Relic One, and troubleshoot common startup failures.
Getting Started with New Relic Distributed Tracing for Java Microservices
Learn how to enable New Relic Distributed Tracing in a Java microservice stack, configure sampling, verify header propagation, and balance observability with cost. Practical steps, code snippets, and troubleshooting tips included.
Hunting Latency Spikes in Kubernetes with New Relic Distributed Tracing
Stop guessing where latency lives in your Kubernetes cluster. Learn how to use New Relic Distributed Tracing to map request flows and pinpoint the exact service or external API causing delays.
Data ingestion rate limit exceeded: New Relic agent configuration
The “Data ingestion rate limit exceeded” error appears when an agent sends more trace or event data than the plan allows. In a low‑traffic application, enabling full transaction tracing or distributed tracing can trigger this limit and inflate the bill. New Relic offers a global or per‑agent trace_sampling setting and a transaction_tracer.enabled toggle that
New Relic Java Agent HikariCP Pool Exhaustion Timestamp Granularity Limits
The goal is to determine whether the New Relic Java agent records the exact moment a HikariCP connection pool reaches its maximum size, or only reports aggregated connection counts at each harvest window. The agent collects pool metrics on a default 60‑second harvest cycle, and Java agent 8.x renamed the metric namespace from Database/ConnectionPool/* to Dat