support: provide option to stringify log body directly in OTEL exporter

[meetzaveri]

Is your proposal related to a problem?

In some observability tools, when connected as logs receiver directly to Hasura's OTEL exporter, it fails to capture some of the details (as opposed to traditional logs exporter i.e. non-OTEL).

Specifically in case of New Relic, when we directly use New Relic OTEL endpoints in Hasura OTEL Exporter, some details such as request body log (JSON object) wouldn't get captured. This is because the New Relic expects a JSON string, whereas the input it gets is JSON object body . You would need an OTEL collector in middle to transform from JSON object to JSON string.

Describe the solution you'd like

Provide a UI as setting (option) to enable this transform by giving user the full control over it. We don't want to make it default behavior which would cause breaking changes to other services.

Describe alternatives you've considered

As a workaround, you can have OTEL collector in middle such as it processes and transforms the JSON log body into JSON string and forwards it to destination/target endpoint.

Hasura OTEL Exporter -> OTEL Collector -> Desired Observability Tool (New Relic Endpoint)

[meetzaveri]

Update:

While we figured out, that New Relic OTEL compliant receiver must be doing non-standard thing by not parsing the JSON body from log. Essentially, if New Relic is providing OTEL endpoint , which we can directly use in Hasura's OTEL exporter, then it should be responsible for transforming JSON object into JSON string. There shouldn't be need of having OTEL collector in first place if New Relic was providing fully functioning OTEL endpoint.

We will reach out to New Relic support to file this as a bug and update the GH issue.