Given deployments to different production environments, ideally it would be possible to distinguish metrics from those environments. E.g. same app deployed to :cluster_a would have separate ecto metrics from same app in :cluster_b. Those separate metrics could be used to create separate dashboards or add filter to existing dashboards for that environment.
Was thinking of something akin to https://hexdocs.pm/telemetry_metrics/1.0.0/Telemetry.Metrics.html#module-breaking-down-metric-values-by-tags, but configurable at PromEx (or plugin) level. We already do similar thing for our OTEL traces, via https://opentelemetry.io/docs/languages/js/resources.
I see that current plugins support metric_prefix. But that was not really what I was aiming for. Metric names would remain the same in this case.
Thank you for your time 🙇🏼
Given deployments to different production environments, ideally it would be possible to distinguish metrics from those environments. E.g. same app deployed to
:cluster_awould have separate ecto metrics from same app in:cluster_b. Those separate metrics could be used to create separate dashboards or add filter to existing dashboards for that environment.Was thinking of something akin to https://hexdocs.pm/telemetry_metrics/1.0.0/Telemetry.Metrics.html#module-breaking-down-metric-values-by-tags, but configurable at PromEx (or plugin) level. We already do similar thing for our OTEL traces, via https://opentelemetry.io/docs/languages/js/resources.
I see that current plugins support
metric_prefix. But that was not really what I was aiming for. Metric names would remain the same in this case.Thank you for your time 🙇🏼