Yuna Verheyden

We should already be logging some of this information in the API layer. For example when storing new limits: https://github.com/grafana/tempo/blob/main/modules/overrides/userconfigurable/api/api.go#L104 We currently log timestamp, tenant, the new value and the...

> > When we are updating we also log the current version and value. > > @kvrhdn for clarity, on a successful update we log both the current data and...

This is a Tempo issue, I'll migrate it to grafana/tempo

As [Mario mentioned in slack](https://grafana.slack.com/archives/C01D981PEE5/p1719307712510379), your backend endpoint is most likely invalid. Can you share your config?

Can you share the final tempo configmap? Specifically the `storage` section. It should look something like this generally ```yaml storage: trace: backend: s3 block: version: vParquet4 s3: bucket: endpoint: s3.dualstack.us-east-2.amazonaws.com...

I think this code is causing the issue: https://github.com/grafana/tempo/blob/e33d407c5de4132468307db880d84d7d542710bd/modules/generator/config.go#L130 When we initialize the service graph processor, we copy the setting from the overrides without checking if a value is already...