file_sd_configs and renaming mertics

[Hossman12]

I'm using file_sd_configs on my remote prometheus instances nad they are being federated into a central location.   The federation job currently filters out all the "go" metrics.  I have an application team that wants to rename the "go" metrics to say "app_go..."  so that they will be federated up for their specific application.  I cannot remove the filter at the fedration level due to the negative impact on the enviorment.  

[Christian Hoffmann]

Hi,

Basically this sounds like it could work using metric_relabel_configs.
However, it also sounds like an anti-pattern, both the "let's federate
(almost) everything" part and the "let's find a workaround for a
specific team".

Maybe you should look into empowering the team to work with "their"
Prometheus instance and try to keep the federated metrics at a minimum
(meta monitoring, job-level stuff)?

Kind regards,
Christian

[Hossman12]

So I have a working config renaming the metrics in the job in my main yaml file.    Is it possible to put this in file_sd_config file?

    metric_relabel_configs:

# Rewrite the Metric Name pre-pending a new prefix

      - source_labels: [__name__]

        regex: "(^targetmetric_.*)"

        target_label: "__name__"

        replacement: "new_prefix_$1"

[Brian Candler]

No. The actual file_sd targets file contains only targets and labels:

https://prometheus.io/docs/prometheus/latest/configuration/configuration/#file_sd_config

The relabelling goes in the scrape job in the main prometheus config file.