List view
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/1 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•2/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•4/4 issues closedImplement 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•4/4 issues closed
Add instrumentation as needed to link Azure App services https://new-relic.atlassian.net/browse/NR-401904
Due by July 18, 2025•1/1 issues closedAdd instrumentation for Azure SQL and data needed to link to APM https://new-relic.atlassian.net/browse/NR-401898
Due by July 4, 2025•1/1 issues closedAdd instrumentation to link to Azure redis services https://new-relic.atlassian.net/browse/NR-401831
Due by July 31, 2025•1/1 issues closedAdd support for Azure service bus instrumentation and relationships. https://new-relic.atlassian.net/browse/NR-401829
Due by June 30, 2025•1/1 issues closed1. Add instrumentation support for spring kafka. 2. Fix any issues with current kafka library instrumentation. https://new-relic.atlassian.net/browse/NR-400766
Due by June 27, 2025•1/1 issues closedhttps://new-relic.atlassian.net/browse/NR-351926 - link to feature https://new-relic.atlassian.net/browse/NR-400761
Due by September 26, 2025KTLO https://new-relic.atlassian.net/browse/NR-400755
Due by July 4, 2025•11/11 issues closedShoring up a hybrid NR/OTel agent for a potential limited access. FY26Q1 Deliverables: Fix issue with bi-directional context propagation between NR and OTel Identify automated testing strategy to support a hybrid agent Explore ways to eliminate requiring the OTel SDK autoconfigure dependency for customers https://new-relic.atlassian.net/browse/NR-399212
Due by June 30, 2025•5/5 issues closedPlacehold for KTLO https://new-relic.atlassian.net/browse/NR-355501
Due by April 11, 2025•18/18 issues closedPlaceholder for any AC Integration support https://new-relic.atlassian.net/browse/NR-355499
Due by March 14, 2025•1/1 issues closedQ4 exploration into the feasibility of creating a hybrid NR/OTel agent. FY25Q4 Deliverables: - Explore approach for using OTel bytecode instrumentation in hybrid agent - Investigate bi-directional context propagation between NR and OTel - Identify automated testing strategy to support a hybrid agent https://new-relic.atlassian.net/browse/NR-355497
Due by March 31, 2025•3/3 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q3, the Java Agent Team will add new instrumentation support for the Redshift Cluster service, emitting data needed for entity linking. https://new-relic.atlassian.net/browse/NR-321528
Due by January 31, 2025•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q3, the Java Agent Team will add new instrumentation support for the App Sync service, emitting data needed for entity linking. https://new-relic.atlassian.net/browse/NR-321518
Due by April 2, 2025•1/1 issues closed**Summary** To support [NR-310852](https://new-relic.atlassian.net/browse/NR-315883) the APM agents will need to be able to add static key/value pairs to the log data being enriched/forwarded by the APM agents for each log message. **Acceptance Criteria** - Users are required to opt-in/enable custom tagging by enabling in agent configuration - Agent default is off (will apply to new installations/customers) - When the feature is enabled all label key/value pairs will be added to each log line - This should apply however the labels are set (i.e. config file, startup option, environment variables) - (Optional?) provide configuration to include/exclude labels. https://new-relic.atlassian.net/browse/NR-317389 https://new-relic.atlassian.net/browse/NR-357485
Due by March 31, 2025•1/1 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-317227
Due by December 31, 2024General customer facing agent enhancements & feature requests. Best effort priority. https://new-relic.atlassian.net/browse/NR-317161
Due by December 31, 2024•1/1 issues closedQ3 exploration into the feasibility of creating a hybrid NR/OTel agent. **FY25Q3 Deliverables:** - Complete necessary research spikes around feasibility of using OTel library instrumentation from within our NR proprietary agent - Review the “Saxon PR” related to library instrumentation to determine applicability in a hybrid agent - Identify automated testing strategy to support a hybrid agent - Write test applications to vet the approach - Create project related branch in the repo, prototyping agent changes - Create a technical paper summarizing the approach, findings and potential next steps https://new-relic.atlassian.net/browse/NR-310851
Due by December 31, 2024•4/4 issues closedOngoing support for agent integration with AC/FC. Specifics TBD. https://new-relic.atlassian.net/browse/NR-310850
Due by December 31, 2024•3/3 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships. Discovery, instrumentation and validation to update the agent to emit data needed for entity linking for the AWS Kinesis Delivery Stream (aka "Firehose") service. https://new-relic.atlassian.net/browse/NR-310353
Due by January 31, 2025•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q3, the Java Agent Team will add support for additional attributes needed for entity linking, which is dependent on the outcome of https://github.com/newrelic/newrelic-java-agent/issues/2003 https://new-relic.atlassian.net/browse/NR-310333
Due by January 31, 2025•2/2 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships. For Q3, the Java Agent Team will add support for a third customer usage scenario, which requires getting the AWS account ID and constructing an ARN for entity linking. Approach to get the account ID will depend on the outcome of https://github.com/newrelic/newrelic-java-agent/issues/2003 and whether deriving the account ID from the AWS accesskey is accepted as a solution. Other APM language agent teams may or may not implement this in the same quarter, depending on outcomes for Java. https://new-relic.atlassian.net/browse/NR-310326
Due by December 31, 2024•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships. For Q3, the Java Agent Team will add support for a third customer usage scenario, which requires getting the AWS account ID and constructing an ARN for entity linking. Approach to get the account ID will depend on the outcome of https://github.com/newrelic/newrelic-java-agent/issues/2003 and whether deriving the account ID from the AWS accesskey is accepted as a solution. Other APM language agent teams may or may not implement this in the same quarter, depending on outcomes for Java. https://new-relic.atlassian.net/browse/NR-310325
Due by December 31, 2024•1/1 issues closedCustomer request to support tagging Logstash logs with custom attributes (part of agent log forwarding). https://new-relic.atlassian.net/browse/NR-309343
Due by December 31, 2024Customer submitted feature request to support DT across both Simple SQS & SNS->SQS subscriptions. https://new-relic.atlassian.net/browse/NR-309329
Due by December 31, 2024Agent instrumentation improvements to support the emerging HTTP 2 specifications. (Note : HTTP 3 is **not** in scope) **FY25Q3 Deliverable:** - Complete a discovery spike to catalog all the supported libraries/frameworks that need to be checked for proper HTTP 2 functionality - Identify a suitable testing strategy that can be employed for each library/framework to determine whether the agent instrumentation produces the expected telemetry or not - Create new GitHub issues for for those libraries/frameworks deemed “broken” - Break/fix, retest as needed https://new-relic.atlassian.net/browse/NR-307029 --- The work is basically: - Identify which of our instrumented libraries/frameworks support HTTP/2. - Create HTTP/2 apps so that we can test our instrumentation for libraries/frameworks that support HTTP/2. - If the instrumentation isn’t working for the HTTP/2 requests, then we need to figure out how to address that. The approach is likely to vary from instrumentation module to instrumentation module. - Ideally, when an instrumentation module is working for HTTP/2 requests we should then add the HTTP/2 test app and appropriate tests to our AITs. The approach that I would recommend would be to compile a comprehensive list of all instrumented libraries/frameworks that support HTTP/2. If that list ends up being pretty large then we should probably narrow it down to a small list of high priority libraries/frameworks to focus on. Once everything on the HTTP/2 list has been resolved then we repeat the entire process for HTTP/3.
Due by December 31, 2024•2/2 issues closedBug fixes, instrumentation improvements, etc. https://new-relic.atlassian.net/browse/NR-307026
Due by December 31, 2024•9/9 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships. For Q2, this includes designing and implementing a new agent API to allow customers to specify either the AWS account-id or ARN for use with matching for the DynamoDB service. For Q3, implementation of the new agent API. https://new-relic.atlassian.net/browse/NR-302482
Due by December 31, 2024•3/3 issues closedAdd support for disabling AI Monitoring in the Java Agent, at the account/org level https://new-relic.atlassian.net/browse/NR-286327
Due by September 30, 2024•1/1 issues closedVarious Java Agent instrumentation improvements and bug fixes for non-core frameworks & technologies https://new-relic.atlassian.net/browse/NR-279688
Due by September 30, 2024•8/8 issues closedVarious development efforts related to integrating the Java Agent with FM/SA. https://new-relic.atlassian.net/browse/NR-279521
Due by September 30, 2024•5/5 issues closedAgent2Query end-to-end testing service ownership is being transferred to agent teams. As part of that responsibility, teams need to: - Implement automation so that new agent releases are used by the Agent2Query service (Note : most APM teams have done this in Q1, so guidance can be taken from that work) - Meet the requirements of [own-your-component](https://newrelic.atlassian.net/wiki/spaces/TDP/blog/2023/11/28/3092121138/Own+your+Component) (OYC) standardization https://new-relic.atlassian.net/browse/NR-278278
Due by September 30, 2024•3/3 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for Elasticsearch clusters, so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277012
Due by February 14, 2025Cross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for the AWS Cognito auth service, so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277009
Due by September 30, 2024•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for the AWS Kinesis Stream service, so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277007
Due by September 30, 2024•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for AWS Lambdas (via AWS SDK), so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277005
Due by September 30, 2024•2/2 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for AWS Lambda aliases (via Lambda URL), so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277003
Due by September 30, 2024•1/1 issues closedCross team collaborative efforts to capture, emit and process needed data for supporting AWS service entity relationships For Q2, the Java Agent Team will take the lead on researching, coding and testing the emitting of sufficient data for the AWS Event Service, so that entity relationships can be created https://new-relic.atlassian.net/browse/NR-277001
Due by September 30, 2024•1/1 issues closedNew asks specific to AWS ECS & Fargate containers https://new-relic.atlassian.net/browse/NR-274481
Due by September 30, 2024•3/3 issues closedVarious KTLO, Java Agent instrumentation improvements and bug fixes for core frameworks & technologies https://new-relic.atlassian.net/browse/NR-272852
Due by September 30, 2024•16/16 issues closedImplementation of the k8s Operator Pattern for the Java Agent https://new-relic.atlassian.net/browse/NR-260140
Due by June 28, 2024•3/3 issues closedAdd support for Apache Pekko. This includes instrumentation for the core Pekko Actor library as well as Pekko HTTP. https://new-relic.atlassian.net/browse/NR-252389
No due date•2/2 issues closedVarious documentation improvements for the Apr-Jun quarter. https://new-relic.atlassian.net/browse/NR-248060
Due by June 28, 2024•3/3 issues closedhttps://new-relic.atlassian.net/browse/NR-237622
No due dateImplement Auto Scaling for the Angler service. https://new-relic.atlassian.net/browse/NR-238913
Due by September 30, 2024•1/1 issues closedExisting instrumentation enhancements, bug fixes, etc. https://new-relic.atlassian.net/browse/NR-238497
Due by June 28, 2024•13/13 issues closed