Diagnose Cross-Service Latency with New Relic Java Agent Tracing
Connect spans across Java services to find where slow requests actually break down, without guessing from logs alone.
Loading…
ReadMeFeed / Community knowledge
#java-agent
Real questions. Useful conversations. Find the people who know your stack.
newrelicGetting Started with OpenTelemetry Java Agent for Zero‑Code Tracing
Learn how the OpenTelemetry Java agent adds automatic tracing to Java apps without code changes, covering setup, a Spring Boot example, and practical limits.
opentelemetryAdd Custom Attributes to New Relic Java Agent Transactions
Learn how to enrich New Relic APM traces with custom key‑value pairs (e.g., user‑role, tenant‑id) using the Java agent API, verify the data, and roll back safely if needed.
Does New Relic's Java agent guarantee heap dump capture when memory usage exceeds the configured threshold in a Kubernetes pod with restricted capabilities?
Determine whether New Relic's Java agent guarantees heap dump capture whenever the configured memory‑usage threshold is exceeded, especially when the JVM runs inside a Kubernetes pod with limited Linux capabilities. The agent’s automatic heap dump is described as a best‑effort feature that relies on HotSpot diagnostic commands (jmap/jcmd) and requires the pr
kubernetesNew 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
Unable to load instrumentation class in Spring Boot 3.x with Java 17
p>When deploying a Spring Boot 3.x application running on JVM 17, the New Relic Java agent occasionally fails to capture specific transaction traces. While the agent initializes, the application logs indicate a failure to load certain instrumentation classes during the bootstrap phase. The issue appears to stem from a mismatch between the agent version an
Automatic vs Manual Instrumentation for JDBC Connection Pool Exhaustion
Diagnosing intermittent connection pool exhaustion in high-throughput Java applications requires a balance between visibility and performance overhead. OpenTelemetry provides two primary paths for capturing this telemetry. Automatic Instrumentation The OpenTelemetry Java Agent provides out-of-the-box visibility into JDBC connection pools, capturing span even
New Relic Java APM agent: Determining effective app_name when both newrelic.yml and environment variable are set
Goal: guarantee that a single deployable image produces the same New Relic APM entity name regardless of the environment it runs in. Uncertainty: when both newrelic.yml defines app_name and the NEW_RELIC_APP_NAME environment variable (or JVM system property) are present, the agent’s precedence rules determine which value wins, and those rules can differ acro