perfsonar-user - [perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts.

Subject: perfSONAR User Q&A and Other Discussion

List archive

[perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts.

From: Phil Reese <>
To: "" <>
Subject: [perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts.
Date: Wed, 18 Oct 2023 14:39:05 -0700
Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=stanford.edu; dmarc=pass action=none header.from=stanford.edu; dkim=pass header.d=stanford.edu; arc=none
Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=uxSgoHFycatq+yXWpaN1EfcvUHn6eCbMfuhqzwrbZqI=; b=kXN8xK8VLCxCmQmalz66vULLYweJGXMnVKcTu6Q8dyGywC3WxEFOpxx97TzVjzBEvmrtK4LiOAfvX3kY8sEmOR/w1GcEl1wyEekdpCsOvPiDxrUOGueHwkSZfGqSdQR4leEaVaVhsqwz9nqzyswgFLn2GeBLLk4O8lf2KvmnLv+rvVIbGgP6jQdig3p4lT3JPUNHJGtd/DWKQ1a2pJiNRLpNURdQ1svj/gA2cZfNoF3/75GHO1yjDNw4f/W/ViRc2VfXBMKTJVKa48tdHyRiQ4s01NNFxdeUkfzlqkURx3A4THpZIofwDYWI3Ydip+TYonXFXpTv+WWj7jv5aKYcqg==
Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TlXgTYdMvkE0H5+1s9NI/+Lp0ABo4bFDvNNWsNU0Vknrq+CN+2koWJ9cXmsIqEWtRCvjn3p37Bs+fJv0kvF5D24JsfsgV1NC0gNn5rvUeSi6toi7eaxvTz+7+tX4OFdDlEWM6LxZvGDSSANKsG0+zCu+F4xJR2XV/ix2A8yFNbjpZyDOGj81N0waxwpNlfZjYydBUu3gZBvzgKqEoM1ja+QOlHxLTRxtYnoKbW/Nvj6LLAZkgCAItY/Rk2aWvVAWrK8gWNL1LfMRalvlhCzn/FM5E7ySUZDE3/fd5UOeciQkis1FWmkdvvh2GCk5Dne38Rx02kMnL5416vGPksrRfQ==

Hi,

I've tried a couple of variants without success.

I'm trying to run the perfSONAR Achive on one host and run a perfSONAR MaDDash server on a second host.

The Testpoints are reporting well to the Archive host (my.archive) with a similar stanza to this in my .json file:
{
    "archiver": "http",
    "data": {
        "schema": 3,
        "_url": "https://my.archive/logstash",
        "verify-ssl": false,
        "op": "put",
        "_headers": {
            "x-ps-observer": "{% scheduled_by_address %}",
            "content-type": "application/json"
        }
    },
    "_meta": {
        "esmond_url": "https://my.archive/esmond/perfsonar/archive/"
    }
}

I've added the same .json file used on the Testpoints and Archive host to the MaDDash host. The maddash-webui page on the Maddash host shows the grids, as expected, but it never retrieves data from the Archive hosts.

I've switched the 'esmond_url' line in the MaDDash .json file to be:
"esmond_url": "https://my.maddash/esmond/perfsonar/archive/"

No change.

I've changed the whole archive stanza to be:
{
    "archiver": "http",
    "data": {
        "schema": 3,
        "_url": "https://my.archive/logstash",
        "verify-ssl": false,
        "op": "put",
        "_headers": {
            "x-ps-observer": "{% scheduled_by_address %}",
            "content-type": "application/json"
        }
    },
    "_meta": {
        "esmond_url": "https://my.maddash/esmond/perfsonar/archive/"
    }
}

And put it into use on all Testpoints and Archiver, but no data is showing up on the MaDDash grids.

Suggestions for combo of my.archive and my.maddash I should be using?

Thanks,
Phil

[perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts., Phil Reese, 10/18/2023
- Re: [perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts., Andrew Lake, 10/19/2023

List archive

[perfsonar-user] Running perfSONAR Archive and MaDDash on separate hosts.