Closed Starefossen closed 1 month ago
sure :smile:
if someones stumbles on how to configure that:
1) download their tempo-config in a local dir
2) bind your local tempo-confg.yaml to their container:
volumes:
- ${PWD}/docker/otel-lgtm/tempo-config.yaml:/otel-lgtm/tempo-config.yaml
3) configure tempo config, for example with:
overrides:
metrics_generator_processors: [service-graphs, local-blocks, span-metrics]
max_bytes_per_trace: x
use this link
to understand which key you can use, we have to use legacy config and you cannot refer to grafana docs sadly.
if someones stumbles on how to configure that:
- download their tempo-config in a local dir
bind your local tempo-confg.yaml to their container: volumes:
- ${PWD}/docker/otel-lgtm/tempo-config.yaml:/otel-lgtm/tempo-config.yaml
- configure tempo config, for example with:
overrides: metrics_generator_processors: [service-graphs, local-blocks, span-metrics] max_bytes_per_trace: x use this link
to understand which key you can use, we have to use legacy config and you cannot refer to grafana docs sadly.
Documentation and source code would be here.
docs
source codes
If you want to have more advanced configs, you can do so by mounting config files like here:
Tempo spanmetrics seams to not be enabled, would you accept a PR for that?