Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Modification of Metric Names During Federation #2647

Closed
civik opened this Issue Apr 20, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@civik
Copy link

civik commented Apr 20, 2017

It would be useful to have the ability to 'prepend' / 'modify' / 'insert from label' the metric names upon federation.

Take the use case of pulling metrics from tenant environments where user metrics are scraped and given tags widget_metric{job="userdata", namespace="bobsnamespace"} . To avoid polluting the 'root' metrics and enforce some sort of namespacing onto users in a multi-tenant environment, I would federate and insert values from tags into the metric name and end up with a metric: userdata_bobsnamespace_widgit_metric

- job_name: 'federate-user'
  scrape_interval: 15s

  honor_labels: true
  metrics_path: '/federate'
  
 --> transform_metric: 
        prepend:
        - '{{job}}_{{namespace}}'  <--

  params:
    'match[]':
      - '{job="userdata"}'
   
@brian-brazil

This comment has been minimized.

Copy link
Member

brian-brazil commented Apr 20, 2017

This is already possible via metric relabelling, however adding a label instead would be recommended instead of changing the metric name as labels are how you namespace such things.

Usage questions are best asked on https://groups.google.com/forum/#!aboutgroup/prometheus-users

@lock

This comment has been minimized.

Copy link

lock bot commented Mar 23, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Mar 23, 2019

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.