This message was deleted.

The level is set for service telemertry part which is for collector warn/error log purposes. You need to use logging exporter to see the data on console. It won't be JSON but prettified trace/metric.

thanks Srikanth. I have set it up as follows under exported:

logging:
    loglevel: debug

but still the data is not getting printed on console. If I have to send the data in JSON, can I configure it as follows:

otlphttp/json:
    endpoint: <https://example.com:4318/v1/traces>

If I have to send the data in JSON, can I configure it as follows:

Do you mean send it from the instrumented application?

No, need to export data from exporter/collector as json

I am not following. What are you trying to achieve? The

logging

exporter exists for debugging purposes and just prints the data to console.

ok, let me go point by point.

logging:
    loglevel: debug

This configuration is not helping, not able to see the trace data in console. THis is given under exporters section.

Is it part of any traces pipeline in the config?

THanks, I added it in the pipeline and it is working now :-) My second point is: how do I sent it as Json over http ? what is the configuration for it ?

how do I sent it as Json over http ?

What do you mean by this? Where do you want to send it to?

I need to export the data in json format...it has to be exported to http end point. Currently, it is getting exported as prettified format

You can use OTLP/HTTP exporter to do that

It is expecting the port number: Exporting failed. Will retry the request after interval. {"kind": "exporter", "name": "otlp/http", "error": "rpc error: code = Unavailable desc = connection error: desc = \"transport: Error while dialing dial tcp: address example.com/deeptrace: missing port in address\"", "interval": "3.358221818s"} Here is the configuration: otlp/http: endpoint: http://example.com/deeptrace