pure_exporter

[Andrew Meyer]

While I know the pure_exporter is not full supported by prometheus I'm trying to find out if this is potentially a timeout issue.

Currently I have the pure_exporter set up using a docker container on RHEL 7.9.

My configuration in prometheus is setup like this:

  # Job for all Pure Flasharrays
  - job_name: 'pure_flasharray'
    metrics_path: /metrics/flasharray
    scrape_timeout: 1m
    scrape_interval: 3m
    relabel_configs:
    # meta label of target address --> get parameter "pure_host"
    - source_labels: [__address__]
      target_label: __param_endpoint
    # label of target api token --> get parameter "pure_apitoken"
    - source_labels: [__pure_apitoken]
      target_label: __param_apitoken
    # display the pure host as the instance label
    - source_labels: [__address__]
      target_label: instance
    # point the exporter to the scraping endpoint of the exporter
    - target_label: __address__
      replacement: 127.0.0.1:9491 # address of the exporter, in debug mode
                                  # THIS NEEDS TO BE CHANGED TO YOUR ENVIRONMENT

    file_sd_configs:
    - files:
      - '/etc/prometheus/pure_flasharray_targets.json'

When I go to check the current targets for this I see the following:

Get "http://1.2.3.4:9491/metrics/flasharray?apitoken=API-TOKEN&endpoint=storage01.example.com": EOF

Any thoughts?  I am getting little help from the github issues page for the project.

Thanks!

[Brian Candler]

Where did that obfuscated IP address 1.2.3.4 come from?  If it's not 127.0.0.1 (which you didn't need to obfuscate) then the error message suggests that your rewrite rule on __address__ isn't working.

Try including the address:port in quotes:

    - target_label: __address__
      replacement: '127.0.0.1:9491'

(Colons have special meaning in YAML if you're not careful, so always safest to quote)

[Andrew Meyer]

The obfuscated IP came from the Prometheus server targets page.  Also I am only having a problem with storage array.  Everything else works.