Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] MaDDash Reporting Data (Combining Reverse and Forward Test Results)

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] MaDDash Reporting Data (Combining Reverse and Forward Test Results)


Chronological Thread 
    < Chronological >      < Thread >
  • From: Mark Feit <>
  • To: Travis Cook <>, "" <>
  • Subject: Re: [perfsonar-user] MaDDash Reporting Data (Combining Reverse and Forward Test Results)
  • Date: Mon, 29 Nov 2021 21:10:14 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=internet2.edu; dmarc=pass action=none header.from=internet2.edu; dkim=pass header.d=internet2.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=G59RG1r9Y0w1pejlT4IO4r2ydfvwJ1bXrG6irubxNmE=; b=dtIKfkMQSk9Lh4x1uAv8c3uXanrB0JnW5T/rUVlZX06uO97m1YpGPG8P8Z6ERtcXlX7+TWkxmuk5dK7ipLQmgR8cUPmDIJ1ulrvnbuzyBmn7QG5o0U6LOmTGDOfTqKG9/TBQYN+EtLvQQnkbHzGTOtA+aW7u5Fqj8fdwAQIrypziE8xuw3qOoKaN1Wn91Qlz58ju/zFcxVs/Yx3p6s6SeN/0gGd6I4tXFCRr4zmMQMN7OWQwkwbcwG99JweMsBh2FmbbJE+sMDo0oO3+YKfNXYyTQ5kFKAnPRsxtXCUS5fd8WV3/nGe7MRYS3NPd6PNBsted/6boDspj/5N5Y2pLQQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lm/QNGht26drS3Vz91BjO0Wp4OSOAZAuxvJg2xfkp8dtkTwU66ApRNQ0fEBxCgKMqeyhyGGN8mupmo2z/YIW3SJG3mbkGbKKfR3OyaVxE7BXNnBY6+pmnOdGds5ZbKXvu6cYGXexkSXeGAMoH7sNdNY6yZgwNIbcqPSN2ZvRGoEwRALVdWgXR74TkEoUu1eH5PnJ15GAe8YXqDVCS1CajjhICbXCM2KbNQiOjKC0EX740uf1ittoRXYoHaYLGwlH+2wjcn7HMrh68hFITmI0tQ4tFM6FKGRHUbuUVPnUGoXRye2plv3l8YfvjZLeBfmPYvhpChC1BBXuxpS84LXWfQ==

Travis Cook writes:

 

Node1 can perform tests with the other
perfSONAR nodes in our network, but our perfSONAR devices can't perform tests
on Node1 due to it being protected by its private network's NAT. To account
for this, we ran reverse tests from Node1 to test the connectivity from other
devices to Node1.

…
Is there a way to
separate the data so that the reverse test data will be in column where Node1
is the destination and not the source?

 

The easiest route to that would be to use a transform while archiving those measurements to rearrange the test specification to make it look like a forward measurement.   (How this is done is covered in our jq tutorial here: https://youtu.be/FrT6R75M3BE?t=2678.  If you haven’t used jq, you can start from the beginning.)

 

The jq for that would look something like this:

 

if .test.type == "throughput" and .test.spec.reverse

then

  # Swap the source and destination and make the test look forward

    .test.spec.source as $old_source

  | .test.spec.source = .test.spec.dest

 | .test.spec.dest = $old_source

  | .test.spec.reverse = false

 

else

  # Anything else gets left alone.

  .

end

 

The catch is that your test must have an explicitly-specified source and destination or you’ll end up with archived measurements that have a source but no destination.

 

Hope that helps.

 

--Mark

 


Archive powered by MHonArc 2.6.24.

Top of Page