perfSONAR User Q&A and Other Discussion

[Johann Hugo <>]

Thanks

If I write to both esmond and opensearch, should I define two archives, or add it to the raw JSON file like this?

{
      "archiver": "http",
      "data": {
        "schema": 3,
        "_url": "https://perf-dash.sanren.ac.za/logstash",
        "verify-ssl": false,
        "op": "put",
        "_headers": {
          "x-ps-observer": "{% scheduled_by_address %}",
          "content-type": "application/json"
        }
      },
      "_meta": {
        "esmond_url": "https://perf-cm.sanren.ac.za/esmond/perfsonar/archive/"
      }

}

I ran into another issue with psconfig-grafana-agent. Grafana + the database is running on an archive host. I can see the opensearch database https://perf-dash.sanren.ac.za/opensearch. 

tail -F /var/log/perfsonar/psconfig-grafana-agent.log

2025-04-14 07:51:12 INFO pid=58363 prog=<module> line=93 msg=Starting pSConfig Grafana agent
2025-04-14 07:51:12 INFO pid=58363 prog=<module> line=104 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 msg=Running agent...
2025-04-14 07:51:12 INFO pid=58363 prog=resolve_address_multi line=110 msg=v6 lookup failed. Cannot resolve address perf-dash.sanren.ac.za. Error Message - The DNS response does not contain an answer to the question: perf-dash.sanren.ac.za. IN AAAA
2025-04-14 07:51:12 INFO pid=58363 prog=reverse_dns_multi line=138 msg=dns reverse lookup failed for fe80::250:56ff:fe9e:cabf%ens160. Error Message - Text input is malformed.
2025-04-14 07:51:12 WARNING pid=58363 prog=_gf_set_home_dashboard line=710 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 pscheduler_assist_url=https://localhost/pscheduler msg=Unable to set home dashboard: HTTP Error - 403 Client Error: Forbidden for url: https://localhost/grafana/api/org/preferences
2025-04-14 07:51:12 WARNING pid=58363 prog=_run_handle_psconfig line=252 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 config_src=remote config_url=https://perf-pwa.sanren.ac.za/pub/config/sanren_100g_servers.json?format=psconfig msg=No display config for task 100G latency. Skipping.
2025-04-14 07:51:12 ERROR pid=58363 prog=_gf_create_datasource line=586 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 config_src=remote config_url=https://perf-pwa.sanren.ac.za/pub/config/sanren_100g_servers.json?format=psconfig msg=Unable to create datasource for https://perf-dash.sanren.ac.za/opensearch: HTTP Error - 403 Client Error: Forbidden for url: https://localhost/grafana/api/datasources
2025-04-14 07:51:12 ERROR pid=58363 prog=_select_gf_datasource line=675 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 config_src=remote config_url=https://perf-pwa.sanren.ac.za/pub/config/sanren_100g_servers.json?format=psconfig msg=Unable to find a suitable archive to use as Grafana datasource
2025-04-14 07:51:12 INFO pid=58363 prog=<module> line=106 guid=27ceb13c-8f46-4058-a3df-70c6853362b6 msg=Agent completed running

The Let's Encrypt Certificate Authority requires a public domain name for issuance. It won't issue certificates for localhost or other local development environments. This means psconfig-grafana-agent can't access https://localhost/grafana/api/datasources. 

wget https://localhost/grafana/api/datasources
--2025-04-14 09:05:42--  https://localhost/grafana/api/datasources
Resolving localhost (localhost)... 127.0.0.1
Connecting to localhost (localhost)|127.0.0.1|:443... connected.
ERROR: no certificate subject alternative name matches
        requested host name ‘localhost’.
To connect to localhost insecurely, use `--no-check-certificate'.

wget --no-check-certificate https://localhost/grafana/api/datasources works fine

wget https://perf-dash.sanren.ac.za/grafana/api/datasources works fine. 

Johann

On Fri, Apr 11, 2025 at 5:37 PM Mark Feit <> wrote:

Johann Hugo writes:

 

The Archives menu of PerfSONAR Web Administrator does not have a http archive type. Does it support an opensearch central archive + grafana? What should I select as the Archiver Type? Esmond, RabbitMQ, Raw JSON

 

The raw JSON option covers the bases that PWA doesn’t by letting you specify an archive specification to be passed through to pScheduler, e.g.:

 

{

    "archiver": "http",

    "data": {

        "schema": 3,

        "_url": https://YOUR-ARCHIVE-HOST/logstash,

        "verify-ssl": false,

        "op": "put",

        "_headers": {

            "x-ps-observer":"{% scheduled_by_address %}",

            "Content-Type":"application/json"

        }

    }

}

 

Further documentation on the format is at  https://docs.perfsonar.net/pscheduler_ref_archivers.html#http.

 

--Mark