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!

-- 
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 prometheus-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/prometheus-users/d12867cc-1e66-424c-90dc-d063f1039c7en%40googlegroups.com.

Reply via email to