Zach Leslie

I took some time to deploy this, and it looks pretty good to me. Nice work. Here is a 6 hour window, and you can't really tell when the deployment...

I don't have that metric currently, but I think we can work that up, perhaps next week. I expect the change from grpc -> http will mean there is more...

The error you point to isn't new with this change, so probably safe to ignore, though would be nice to clean up.

Nice work @andreasgerstmayr. Thanks for following up on this.

Try rebasing on `main` and let's see what CI says. `make lint base=main` locally should give some information as well.

I'm sure that could be adjusted, but can you say more about the use case? Does this impact your load test in a way?

I think the default `param.js` should be modified to reduce the number of attributes. Tweak as necessary for your environment. This is likely where most of the memory is going....

I suspect this is related to the `ndots` configuration in the `/etc/resolv.conf`. May we see the resolver configuration please?

I'm seeing [this](https://github.com/open-telemetry/opentelemetry-collector-contrib/issues/9009) issue about changing the queue size, but perhaps we can make a change in the default config, which is [1000](https://github.com/grafana/xk6-client-tracing/blob/c088e8e7f3ff70fca20ee0ef5a0cebcb4feb9df7/vendor/go.opentelemetry.io/collector/exporter/exporterhelper/queue_sender.go#L41). The client is constructed [here](https://github.com/grafana/xk6-client-tracing/blob/c088e8e7f3ff70fca20ee0ef5a0cebcb4feb9df7/tracing.go#L195), and could...

Tempo log level can be configured with the following. ``` server: log_level: debug ``` It doesn't look like we currently expose log_format on the server as a config option.