On Thu, 25 Jun 2020 at 23:00, Murali Krishna Kanagala < [email protected]> wrote:
> Hello everyone, > > We are moving from wmi_exporter to windows_exporter and trying to do it in > a smooth manner. > Our Alerts and Graphs are heavily dependent on WMI metrics and moving to > Windows exporter may cause some issues because of a different metric prefix > (wmi to windows). > We are looking for a temporary solution where we can keep both wmi and > windows exporter metrics. This can be done by running both exporters on the > server and by adding that to scrape config but I am looking for an option > if I can use the relabel features to create a new metric with wmi_ prefix > for every windows_ prefix metric. > > For ex. If i scrape windows_cpu_seconds_total, i want to keep that metric > and also create a new one like wmi_cpu_seconds_total. > > Is there a way in metric relabeling to keep both old and relabeled metrics? > This isn't possible. Relabelling can rename, but it cannot create or duplicate. -- Brian Brazil www.robustperception.io -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/CAHJKeLrW06oWW1pKViTRZcqm0ZdBTvq1x9U_Jn-runKjTQCXqg%40mail.gmail.com.
