[NA] Remove New Relic dependency

[thiagohora]

Details

In order to make it work, we only need to set the disable envvar to false and the the following variables:

      OTEL_EXPORTER_OTLP_ENDPOINT: https://otlp.nr-data.net:4317
      OTEL_EXPORTER_OTLP_HEADERS: "api-key=xxxxxxxxx"

Issues

Resolves #

Testing

The integration was tested locally using a custom API key from our OTEL provider.

Documentation

[andrescrz]

The change looks generally good to me, just a minor recommendation about the configuration.

Please fill up the description template of this PR. I'm missing information, specially about:

• How was this tested?
• Any test follow-up actions after deploying?
• What infrastructure do we need to deploy in order for this to work? Do we require deploying the OTEL agent priorly.
• Does this work directly with New Relic? Or are there any follow-up actions?
• What about Prometheus/Grafana?

[thiagohora]

The change looks generally good to me, just a minor recommendation about the configuration.

Please fill up the description template of this PR. I'm missing information, specially about:

• How was this tested?
• Any test follow-up actions after deploying?
• What infrastructure do we need to deploy in order for this to work? Do we require deploying the OTEL agent priorly.
• Does this work directly with New Relic? Or are there any follow-up actions?
• What about Prometheus/Grafana?

Hi @andrescrz

1. All the changes were tested locally using a test APIKEY and pointing to our provider, New Relic.
2. Next step is to enable it in Staging and validate the setup
3. The agent is automatically downloaded during the application startup. As we are sending data to New Relic, no infra is needed unless we also want to send it to Grafana.
4. Yes, it works out-of-the-box by pointing to the New Relic backend (More in the PR description)
5. Grafana seems to be instrumented via the Kubernetes cluster so far. As I mentioned, we can also send application data to it, but we are not currently doing it, so I would address this in this PR. Maybe @liyaka can clarify it.

[andrescrz]

LGTM, please make sure this is completely enabled after your testing in staging and before going to production.

We don't want to miss the current instrumentation if any problem arises in production.

[andrescrz]

I think it's better that you move ahead and merge this soon, no need to wait. I changed my mind as we can deploy specific tags.

[andrescrz]

I found mutiple opentelemetry libraries for R2DBC. This seems to be an early one in alpha state. Why this choice over others?

[thiagohora]

This is the agent instrumentation, and all modules are in alpha: https://mvnrepository.com/artifact/io.opentelemetry.instrumentation/opentelemetry-r2dbc-1.0. Here is the definition of alpha:

https://github.com/open-telemetry/opentelemetry-java/blob/main/VERSIONING.md#stable-vs-alpha. Basically, they mention such modules don't have backward compatibility guarantees and a few other problems that may require changes from version to version, but that doesn't mean they are not mature.

[thiagohora]

Fixed all issues by setting some envious. I will merge it on Monday