List view
- Due by January 23, 2026•0/1 issues closed
Verify that our OTel metrics approach fully supports the all of the functionality possible with the Metrics API. https://opentelemetry.io/docs/specs/otel/metrics/api/ The following compliance matrix might be useful to a certain extent but be aware that it mixes OTel SDK and API functionality and we are only concerned with supporting the API. https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#metrics Our support for OTel metrics simply configures them to go to a NR ingest endpoint and associates the entity guid with them so that they end up in the APM entity where the Java agent sends its data. Since we're just redirecting OTel metrics and not directly instrumenting the APIs it is likely that we fully support all of the API capabilities but the purpose of this ticket is to verify that. Min OTel Stability - Beta: https://opentelemetry.io/status/ Overall Acceptance Criteria for each agent (For feb scope) Capture metadata/payload of NR metrics vs otel metrics Document any additional configs & dependencies needed to send metrics API , do we support all the otel configs? Document Delta between NR API vs Otel metrics API (name, metadata etc) Confirm that we are adding same additional attributes using NR API vs Otel API (eg: tags/logs) Test all the possible types of Otel metrics (gauge etc.) Fully compliant with agent specs Stretch - Easy customer facing example applications to onboard customers. Document the feature details internally.
Due by October 31, 2025•1/2 issues closedWe currently have no support for the OTel traces API and the goal is to fully support all functionality capable with the APIs. Additionally, it would probably be desirable to enhance OTel traces with linking metadata so that they can be used . The following compliance matrix might be useful to a certain extent but be aware that it mixes OTel SDK and API functionality and we are only concerned with supporting the API. opentelemetry-specification/spec-compliance-matrix.md at main · open-telemetry/opentelemetry-specification Min OTel Stability - Beta: Status Reference - Overall Acceptance Criteria for each agent for LP(Feb scope): Capture metadata/payload of NR spans vs otel spans Document any additional configs & dependencies needed to send NR traces API , do we support all the otel configs? Document Delta between NR API vs Otel trace API (name, metadata etc) Confirm that we are adding same additional attributes using NR API vs Otel API (eg: tags/logs) Test all the possible types of spans Fully compliant with agent specs Stretch - Easy customer facing example applications to onboard customers. Document the feature details internally.
Due by November 21, 2025•0/2 issues closedThis is based on GA plan doc We currently have no support for the OTel Logs API and the goal is to fully support all functionality capable with the APIs. Additionally, it would probably be desirable to enhance OTel logs with linking metadata so that they can be used within the logs in context experience. There is currently some research on a strategy for supporting the Logs API documented in confluence. https://newrelic.atlassian.net/wiki/spaces/INST/pages/4360471472/Supporting+OpenTelemetry+Log+Data+in+our+Agents https://opentelemetry.io/docs/specs/otel/logs/ The following compliance matrix might be useful to a certain extent but be aware that it mixes OTel SDK and API functionality and we are only concerned with supporting the API. https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#logs Min OTel Stability - Beta: https://opentelemetry.io/status/ Link to Node PR - https://github.com/newrelic/node-newrelic/pull/3228 Reference - Overall Acceptance Criteria for each agent(Feb scope): Capture metadata/payload of NR logs vs otel logs API (eg: tags to logs/ additional attributes to support logs in context) Document any additional configs & dependencies needed to send logs , do we support all the otel configs? Document Delta between NR logs vs Otel logs API (name, metadata etc) Confirm that we are adding same additional attributes using NR logs vs Otel API (eg: tags/logs) Test all the possible types of Otel logs API? Create Agent spec for logs support Fully compliant with agent specs Easy customer facing example applications to onboard customers (Piggy back on otel metrics application) Document the feature details .
Due by October 31, 2025•1/4 issues closed- Due by November 28, 2025•2/10 issues closed
- Due by September 26, 2025•2/7 issues closed
Implement the must-have functionality of the existing OTel hybrid agent bridge. The main goal is that any custom code written against the OpenTelemetry APIs for Logs, Traces, and Metrics will work. https://docs.google.com/document/d/1M_05cXyzI-gVYnaMM5jeTsRNGIqXvd1mF3GMgcnGAPE/edit?tab=t.0 Confluence docs on this work: https://newrelic.atlassian.net/wiki/spaces/INST/pages/3539599389/OpenTelemetry+Agent+Convergence Current WIP is found on this branch: https://github.com/newrelic/newrelic-java-agent/tree/saxon/replace-otel-spans2 Previous milestones: https://github.com/newrelic/newrelic-java-agent/milestone/78 https://github.com/newrelic/newrelic-java-agent/milestone/85 https://github.com/newrelic/newrelic-java-agent/milestone/88
Due by September 30, 2025•4/5 issues closed- Due by September 30, 2025•2/2 issues closed
This is an exploratory effort to prove out the feasibility of a NR distribution of the OTel Java agent. NR distro project: https://github.com/newrelic/newrelic-opentelemetry-java-agent The main goal is to have a distro that is bundled into our existing Java agent jar, can send data to the existing agent collector endpoints, implement the logic for sending data for a few data types (metrics, spans), and have the OTel distro report as a proper APM service entity type. General requirements, questions, and concerns are detailed in the following doc: https://docs.google.com/document/d/1SC7GHgFWhsbrbN7TRaHRoh-PATd3YuskxBob6_ADZds/edit?usp=sharing
Due by March 20, 2026•2/7 issues closedhttps://new-relic.atlassian.net/browse/NR-401361
Due by September 25, 2025•0/7 issues closedhttps://new-relic.atlassian.net/browse/NR-351926 - link to feature https://new-relic.atlassian.net/browse/NR-400761
Due by September 26, 2025[FY26Q1] [Java] Performance Benchmarking (OATS Replacement) Need performance benchmarking tool that can be executed every release to catch any performance regressions. CPU / memory / network / etc? Other options to explore Option 1: Agent soak test https://nerdlife.datanerd.us/new-relic/java-agent-soak-test https://source.datanerd.us/java-agent/jenkins/tree/master/soak-test https://nerdlife.datanerd.us/new-relic/java-agent-soak-test/java-agent-soak-test-runbook Option 2: Jmeter on spring pet clinic app https://new-relic.atlassian.net/browse/NR-400752
Due by September 30, 2025•5/7 issues closed**Q3 FY’25 Deliverable - Milestone 2 : In Scope for Quarter (Q3FY25) for Agent teams: Update test definitions to verify the data types - Transaction Events (Verify transaction events are sent with all the data needed) - ErrorEvents - Error Traces https://new-relic.atlassian.net/browse/NR-317187
Due by October 31, 2025•0/1 issues closed