dealing with label collision on namespace

[underrun]

wrestling with running a workload that has it's own concept of "namespace" - I have a bunch of rules and dashboards set up around that workload with a namespace label that does not mean kubernetes namespace. the workload doesn't need to run in kubernetes (but it can) and i'd like the monitoring setup to work either way. and i was hoping i could reconfigure kube-prometheus to use a label like kubernetes_namespace rather than just namespace.

looks like the kubernetes-mixin has support for namespaceLabel but most of the other components don't seem to have an easy way to manage that.

am i missing something or is the ability to easily reconfigure dashboards, metrics, labels with alternate names to avoid collisions not easily doable?

i looked through issues but i haven't seen people talking much about this.

i could probably make all my dashboards configurable but that feels like the wrong problem for me to solve and would much prefer to just have a static setup that would work anywhere.

thoughts? thanks!