Maxim G.
Maxim G.
Sure, +1 for previous post, we need to completely hide some changes as if they doesn't exist at all. Here is how helm diff does it: ``` test, web-app, ExternalSecret...
It may be acceptable like: ``` ┌ Update ExternalSecret/web-app │ └ Update ExternalSecret/web-app ``` but definitely not as werf.io/sensitive-paths annotation does
`sum(rate(tempo_metrics_generator_processor_local_blocks_flushed_blocks{}[1m]))` shows blocks are flushed. But not to s3 like traces do, they flushed to filesystem instead.
No any errors in the logs
`level=info ts=2025-10-24T18:24:31.32576703Z caller=processor.go:490 org_id=single-tenant msg="flushed block to storage" block=dac71859-5120-44d1-bfc3-2e0bbf8d66c6 `
But all local blocks processor metrics are lost if pod restarts
I mean these: If I restart pod, it will lose its filesystem storage and this screen will start to show metrics from pod restart time.
> So it seems like it's flushing correctly but not to s3? Yes > Pick a metrics-generator pod It's a monolithic deployment, I have no metrics-generator pod. Here is `cat...