Provide trace logs for publishing observability data

[NipunaMadhushan]

Area

Area/Observerbility

Current Limitation

If the user has configured a wrong port of if there is an network connection issue, it wont publish data to our desired data collector/server. We need the trace logs to identify the issue.

We have multiple observability extensions to publish trace data such as jaeger, zipkin and newrelic.
But none of these extensions provide the support to enable trace logs for publishing data.

Suggested Improvement

Provide runtime configuration to enable trace logs as follows.

[ballerinax.jaeger]
agentHostname="localhost"
agentPort=4317
isTraceLoggingEnabled=true

Version

No response

[rizmir22]

Hi @NipunaMadhushan,

Could you please provide an ETA on this?

Regards,
Rizmeer