List view
Research tools available to capture profile data (cpu/memory/ etc..) Prototype to generate profile data(cpu/memory) from agent and display using (0x , platformatic) tools. Learn what data needs to be generated to display NR Flamegraph. Learn how data needs to be generated in the Agent. Compare and contrast with competing products. Validate the requirements/our understanding from feature request -- Definition of Done: 1. Data model (types) we can capture in Flame Graph 2. Knowledge on How to generate the data See this feature request for details - https://new-relic.atlassian.net/browse/NR-383309
Due by November 28, 2025We 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 - Acceptance Criteria: 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 October 24, 2025Verify that our OTel metrics approach fully supports the all of the functionality possible with the Metrics API. 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. opentelemetry-specification/spec-compliance-matrix.md at main · open-telemetry/opentelemetry-specification 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: 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 November 28, 2025•1/1 issues closedhttps://new-relic.atlassian.net/browse/NR-380740 Provide instrumentation for MCP SDK. To mimic [Python’s support](Python agent v10.13.0 ), the agent must instrument and record segments/spans for the following methods on the MCP Client: callTool - Llm/tool/MCP/callTool/<tool-name> readResource - Llm/resource/MCP/readResource/<resource-name> - resource-name is basically the scheme from the uri(i.e. file://foobar.txt would have resource-name of file) getPrompt - Llm/prompt/MCP/getPrompt/<prompt-name> We should also create an example app to demo its use by mixing in calls to openai, sample python app. Note: Python agent provides full path to function, which we typically never do but maybe we rename the function segment to client.callTool , client.readResource, or client.getPrompt Definition Of Done: Example application for customers to show the usage of this feature. Docs updates as needed. Compatibility report updates as needed Versioned test updates. Internal docs updates supportability metrics/dashboard
Due by September 26, 2025•3/3 issues closedWe 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. [Supporting OpenTelemetry Log Data in our Agents| https://newrelic.atlassian.net/wiki/spaces/INST/pages/4360471472/Supporting+OpenTelemetry+Log+Data+in+our+Agents] [OpenTelemetry Logging|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. [opentelemetry-specification/spec-compliance-matrix.md at main · open-telemetry/opentelemetry-specification|https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#logs] Min OTel Stability - Beta: [Status|https://opentelemetry.io/status/] Definition of Done: 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? 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 September 19, 2025[FY26Q2] Node.js Otel bridge
No due date•2/2 issues closed- Due by September 26, 2025
- Due by June 27, 2025•1/1 issues closed
Expand benchmarking tests https://new-relic.atlassian.net/browse/NR-400694
Due by September 30, 2025•8/8 issues closedEpic to track effort for FY26Q1 Node.js otel bridge features. 1. Customer feedback and improvements 2. Automagic configuration of bridge 3. Complete E2E test coverage based on CAT tests 4. Spike on Dependency management with DACI on the feasibility and recommended approach(also looking into other competitors etc) 5. spike and plan for custom dimensional metrics https://new-relic.atlassian.net/browse/NR-400650
Due by June 27, 2025•6/6 issues closedhttps://new-relic.atlassian.net/browse/NR-380740
Due by June 30, 2025•13/13 issues closedhttps://new-relic.atlassian.net/browse/NR-354548 https://new-relic.atlassian.net/browse/NR-359398
Due by May 30, 2025•7/7 issues closedToday customers can only report timeslice metrics through our language agents. The feature ergonomics are lacking. These custom metrics are not dimensional, they are simple flat metric names that must be queried through the “magical” newrelic.timeslice.value metric, hindering discoverability. We will add a new dimensional metric API to our language agents supporting count and summary metrics. Customer Experience Custom metric data will be more discoverable as a normal dimensional metric. DM data is more usable - customers can filter and facet on autocompletable attribute names. The API and data format is closer to modern telemetry apis like OTel. Customers can build dashboards using these metrics, and if they later switch to OpenTelemetry agents, they will be able to report the same metrics into their existing dashboards. A dimensional metric API is a compelling feature that may drive agent upgrades. Full document with details: APM Agent Dimensional metrics API - Google Docs https://new-relic.atlassian.net/browse/NR-191666
No due date- No due date•1/1 issues closed