Gustavo Pantuza

@scorphus I think that would be awesome. If you need any help, let me know!

Hi, @meskio. No problem. I've solved the code conflict. The Pull Request is updated.

Thank you @dmathieu for all the clarifications. I totally agree with everything you have mentioned. And thankfully, the new Spec seems to solve the issue I have tried to report....

I am closing this PR since, based on the suggestion made here, I have opened another Pull Request (#1713) addressing the Open Telemetry Spec.

Yes, indeed it makes more sense to me as well. I will make sure update this PR by changing the `go.mod` and we can check if does the trick.

I have tested it by running `go install` locally and it works by installing a binary with the name `grpc_health_probe` under my `$GOBIN` path. Thank you for the suggestion. Please...

> Sadly changing the module name will break too many users. https://sourcegraph.com/search?q=context:global+go+install+github.com/grpc-ecosystem/grpc-health&patternType=standard&sm=1&groupBy=repo I don't think this is a huge problem. We can just say "if installed via `go install` the...

## TL;DR On the Helm Chart `tempo-distributed` instead of adding a parameter `overrides`, use `global_overrides` as a workaround: ```yaml global_overrides: defaults: ingestion: rate_limit_bytes: 32000000 # 32MB burst_size_bytes: 48000000 # 48MB...

There is a bug on the `distributed-tempo` Helm Chart while parsing this new `overrides` block. I have added the [following comment](https://github.com/grafana/helm-charts/issues/2802#issuecomment-2161285343) on a issue describing how to workaround this problem....

Hi, @kaylareopelle . I would love to try adding this feature.