Bartlomiej Plotka

@discordianfish You are missing important thing here. Prometheus discovers Pod's **ports** not just pods. However because of: * pattern for reusing Pod annotations and limitation of relabel I described [in...

Added some table of **existing solutions** for starting point: https://docs.google.com/document/d/1S6O1czHtjR2DGfK2zeZDLr88wxyLRXB2JpH5g7YM1J8/edit?usp=sharing

> Unless I'm mistaking, prometheus discover two targets for each jobs, but the two targets are exactly the same. Why? If you target __address__ you will get two targets per...

Your second idea is kind of `if` -> relabelling does not allow to use regex build from values from another labels. Regexp is build on config reload time.

2c from my side: Go tools are used not only by Go modules. This is why a separate go.mod for tools or something like what https://github.com/bwplotka/bingo automated for you might...

NOTE: We discussed this topic today on [Prometheus DevSummit](https://docs.google.com/document/d/11LC3wJcVk00l8w5P3oLQ-m3Y37iom6INAMEu2ZAGIIE/edit#). We agreed to implement this. Help wanted.

Considered, if someone has time to experiment and prove it's better vs complexity 🤗

Not sure if we should continue discussion on this thread or separate but FYI we agreed on [the recent Prometheus DevSummit](https://docs.google.com/document/d/11LC3wJcVk00l8w5P3oLQ-m3Y37iom6INAMEu2ZAGIIE/edit#bookmark=id.zcja7rewro81) to store created timestamp in some way (NOT a...

> Asking just to make sure I'm following your line of thought 😅. With the synthetic zero approach, do you have something like this in mind? Not sure if I...

Another issue (could be done in another PR, but ticket would be nice for it): If I specify `/` and `kind1` is not a valid filter OR it's unused filter,...