Changing the Object name in the yaml configs?

[fathom cypress]

Reason:
My metrics will be going to a shared Prometheus instance and it is entirely possible that the object names could overlap the naming convention used by other vendors.

What I have figured out so far:
I have a python script that modifies all the yaml files in /opt/harvest/conf/.. to prepend names like aggr to netapp_aggr. I have gotten a bulk of these to successfully display properly now but I "think" that yaml configs that leverage a plugins: entry do not pickup the updated object naming convention.

Some examples of what I am missing and cannot find where to adjust:
metadata_collector_*
cluster_software_validation
net_route_interface_labels
poller_memory
environment_sensor_*

If I can get this nailed down it will be a huge win for my team.

[dense moon]

hi @fathom cypress you can relabel metrics with Prometheus https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config would that work for what you are trying to achieve?

[fathom cypress]

Hmm...So this is something that would be configured on the Prometheus server. I have full control of my test environment where I have Harvest, the exporter, Prometheus, and Grafana. In live production, I only control Harvest and the exporter. I'm not sure which of the relabel_configs: would achieve what I need.

[dense moon]

yes, it's part of Prometheus's config and should support any relabeling needs you have. There are lots of examples online, here's a decent one https://valyala.medium.com/how-to-use-relabeling-in-prometheus-and-victoriametrics-8b90fc22c4b2

[fathom cypress]

So I guess I would be looking at something like this?
scrape_configs:

• job_name: 'harvest'
  http_sd_configs:
  • url: 'http://10.1.104.172:8887/api/v1/sd'
  • source_labels: [name]
    regex: "(.+)"
    target_label: "name"
    replacement: "netapp_$1"

ugh, the formatting...

[dense moon]

yes, something like that. If you type triple backticks with yaml, you can paste yml safely. e.g.

asar2:
        addr: 10.115.204.152
        collectors:
            - StatPerf
            - Rest
            - RestPerf

[fathom cypress]

Okay, I see what I was missing (or what the article failed to mention) is that the additional config parms needs metric_relabel_configs:...I got it working.

[undone tundra]

@fathom cypressDo you want to prefix all metrics exported by Harvest with a specific string? If so, Harvest supports this by adding global_prefix to the Prometheus exporter settings in your Harvest configuration, as shown below.

Exporters:
  prometheus3:
    exporter: Prometheus
    port: 12880
    global_prefix: netapp_

https://netapp.github.io/harvest/25.08/prometheus-exporter/#parameters

[fathom cypress]

I guess it helps to RTM, I need to spend more time reading...

[dense moon]

there's a lot of manual 🙂

both options: global_prefix and relabeling are useful, but if you only want a prefix on all metrics, global_prefix is easier. Relabeling can do lots more, but if you don't need that power, you don't need it...