Guillaume GILL

@breed808 I don't "know" but seems logic that perflib adds increment for duplicated metrics. So I guess the other similar trick in the "process" collector makes the values a little...

Hello I made a test with your image @zalegrala that seems almost good, the pods are starting correctly, but the query fails. `upstream: (500) error querying ingesters in Querier.Search: rpc...

Maybe an idea, the distributor seems not able to contact the ingest or build it own distributor ring (the error is not clear) But I see there is no `distibutor.ring.prefer_inet6`...

Solution found !!! ```yaml ingester: lifecycler: address: tempodb-ingester-discovery # Replace '[::0]' from your guidelines ``` I'm not really sure if it's "correct" because all the ingester have the same DNS...

Side effect of removing `address`, the querier has a very unexpected error when it calls the ingesters ^^ `transport: Error while dialing dial tcp: address 2600:1f10:4f40:9d02:e6c9::8:9095: too many colons in...

> @gillg Thank you for testing. Much appreciated. Looks like you bumped into the same issue reported on the dskit pr. [grafana/dskit#185 (comment)](https://github.com/grafana/dskit/pull/185#discussion_r1072704469) Indeed! It's related to the way the...

> In my tests, writes worked fine, but reads were failing most of the time. I'll spend a little more time with this soon, but if other testers want to...

Ah... I'm in early deployment stage of tempodb so I don't really have feedback to compare and not yet dashboards. Any query advice I can run on Prometheus directly to...

I'm not sure if it's related, and I don't know if it's part of the spec (seems not) but having a counter-signature by another company (like digicert, globalsign, sectigo, etc...)...

Hum I see, without speaking about "bad actors" you don't want a user being able to "re-sign" an artifact (nevermind if it's the company A which sign again, or a...