Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request - add support to other observability providers (Support New Relic) #646

Open
caioquirino opened this issue Mar 9, 2022 · 3 comments
Labels
discussing The issue needs to be discussed, elaborated, or refined feature-request This item refers to a feature request for an existing or new utility logger This item relates to the Logger Utility

Comments

@caioquirino
Copy link

caioquirino commented Mar 9, 2022

Description of the feature request

Problem statement
We have used the js version of lambda-powertools for a long time already in DAZN, and now we have most of the Back-end teams working with typescript instead of javascript directly. With that said, the interest in adopting this project is really high, and it is useful for many areas already. In order to make the best adoption of this amazing tool in DAZN, it would be great if we could either configure it to use New Relic instead of Cloudwatch, or extend it with our own implementation, so we could keep it self-contained in a single repository.

Currently we are using New Relic for both logging, metrics and tracing in practically all the services in DAZN.

Summary of the feature
Provide a way to configure or extend this tools for external providers (New Relic)

Example suggestions:

Logger options:

  • Add correspondent middlewares for New Relic
  • Propose a way to configure the middlewares to use a New Relic implementation
  • Add some extensibility in the Logger so it's possible to override the printLog function (or something like that) or provide an alternative implementation to the Logger class

Metrics options:

  • Add correspondent middlewares for New Relic
  • Propose a way to configure the middlewares to use a New Relic Implementation
  • Add the ability to provide an alternative implementation to the Metrics class

Tracing options:

  • Add correspondent middlewares for New Relic
  • Propose a way to configure the middlewares to use a New Relic Implementation
  • Add the ability to provide an alternative implementation to the Tracer class

Code examples
To be defined

Benefits for you and the wider AWS community
Developers that needs to use New Relic or any other observability provider are able to use this project

Describe alternatives you've considered
It's briefly documented in the Summary, still needs more understanding of which options are possible

Additional context

Related issues, RFCs

aws-powertools/powertools-lambda-python#1433

@caioquirino caioquirino added the triage This item has not been triaged by a maintainer, please wait label Mar 9, 2022
@dreamorosi
Copy link
Contributor

Hi @caioquirino thank you for opening this issue and formalizing the request!

As we have mentioned during our meeting with the Backend Guild this is something that we are keen to consider.

Please allow us some time to discuss this internally and we'll be back to you and the team.

@dreamorosi dreamorosi added the RFC Technical design documents related to a feature request label Mar 9, 2022
@saragerion
Copy link
Contributor

Thanks for opening this issue @caioquirino!

@dreamorosi dreamorosi changed the title Support New Relic (all): Add Support to other observability providers RFC - Add Support to other observability providers (Support New Relic) May 12, 2022
@dreamorosi dreamorosi added tracer This item relates to the Tracer Utility need-more-information Requires more information before making any calls on-hold This item is on-hold and will be revisited in the future feature-request This item refers to a feature request for an existing or new utility and removed triage This item has not been triaged by a maintainer, please wait RFC Technical design documents related to a feature request labels Nov 13, 2022
@dreamorosi dreamorosi added need-customer-feedback Requires more customers feedback before making or revisiting a decision and removed need-more-information Requires more information before making any calls labels Feb 28, 2023
@dreamorosi
Copy link
Contributor

Hi everyone, we have started working on a RFC for this topic and the first tests are showing that we might be able to support 3rd party observability providers by allowing you to fully customize the log formatter used to emit logs.

If you're interested in reading the current proposal and leaving your feedback please do so at #1500.

@dreamorosi dreamorosi added logger This item relates to the Logger Utility discussing The issue needs to be discussed, elaborated, or refined and removed tracer This item relates to the Tracer Utility on-hold This item is on-hold and will be revisited in the future need-customer-feedback Requires more customers feedback before making or revisiting a decision labels Jun 20, 2023
@dreamorosi dreamorosi moved this from Ideas to Backlog in Powertools for AWS Lambda (TypeScript) Jun 20, 2023
@dreamorosi dreamorosi changed the title RFC - Add Support to other observability providers (Support New Relic) Feature Request - add support to other observability providers (Support New Relic) Jun 20, 2023
@dreamorosi dreamorosi added this to the Version 2.0 milestone Jun 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussing The issue needs to be discussed, elaborated, or refined feature-request This item refers to a feature request for an existing or new utility logger This item relates to the Logger Utility
Projects
Development

No branches or pull requests

3 participants