Arunprasad Rajkumar

I got the mixed result when running benchmark in https://github.com/timescale/promscale/pull/1534 after removal of mutux which is been added as part of https://github.com/timescale/promscale/commit/8a0802c8c3058c5f0e2c0246bb9fee9114979cc2 ``` ~/go/bin/benchstat /tmp/1.txt /tmp/3.txt name old time/op new...

@VineethReddy02 We already have telemetry event around otel ingestion and #1535 is implemented on top of otel. Hence all the events which we send for otel ingestion is also applicable...

I've been exploring following options to enable telemetry, 1. Add metrics in WriteSpan and expose it to telemetry ( similar to e.g. https://github.com/timescale/promscale/blob/master/pkg/jaeger/store/store.go#L64) 2. Expose intrinsic metrics exposed by gRPC...

@niksajakovljevic , the failure is due to raising this PR from my fork.

> For Promscale, I recommend: > > 1. implement write path of remote API > 2. create a new test similar to https://github.com/jaegertracing/jaeger/blob/3d67ac86f53866332568b0f542265b00d86407fc/plugin/storage/integration/grpc_test.go#L189 > that can be configured from cmd...

I think this can be done only after post 0.14.0.

Thanks @fbricon for your suggestion. Similar request has been already logged into our backlog., we will try to prioritise it. https://issues.redhat.com/browse/APPAI-1381

@mathur07 I still see same issue. Can you look into this?

Hey @shiftkey, Sorry for the delay. Why can't we simply fallback to system installed git on unsupported platforms like FreeBSD? Looks like none of the CI services(circleci, travis) are supporting...

@VineethReddy02 @ramonguiu