Lex Rivera
Lex Rivera
Any chance it will be merged? Along with #12766
@LargoUsagi maybe it's time to dig up my old helm chart for FTS?
for tempo-distributed i use following: ```yaml global_overrides: metrics_generator_processors: - service-graphs - local-blocks ``` which gets expanded to following in configmap: ```yaml overrides: metrics_generator_processors: - service-graphs - local-blocks per_tenant_override_config: /runtime-config/overrides.yaml ```...
probably related: https://github.com/grafana/pyroscope/issues/2082
> Hello! > > > Maybe make it more unique to not overlap with existing metrics? Like k8s_cluster, for example, or just give ability to drop it from default values....
@SQLJames nope, i just switched to deploying operator only and every other resource as separate CR. Way more flexible this way.
It will be nice if we can map them in loki config, since there is many variations. warning/WARN, error/ERR, there is also numerical severity in some apps.