Keep Zipkin metadata for namespacing purposes

[NikolaeVarius]

We currently run a single ES backend with multiple namespaces for environments.

While this is fine for zipkin UI which we can filter via tags, the dependency job takes everything and strips out metadata meaning that we have a dependency chart that just merges all environments into one large chart.

We would like a way to have the job query for tags and create seperate charts per namespace

[codefromthecrypt]

So are you saying every trace has a specific tag (ex named namespace?) can you give an example expression and how many of these (roughly) you have?

[jorgheymans]

+1 to something like that. We have several environments (DTAP etc) dumping traces to the same zipkin cluster. So it would be helpful to see the dependency diagram only for a specific environment, based on a tag.

[TechniXC]

+1

[jcchavezs]

Can any of you come up with a PR on this?