Project

General

Profile

Feature #1696

Dashboard: speedtest

Added by Luke Murphey over 7 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
01/19/2017
Due date:
% Done:

100%


Description

  • Inputs:
    • host
    • runs
  • Panels:
    • Recent ping
    • Recent download rate
    • Recent upload rate
    • Historical ping
      • RTT history
      • Average/Min/Max
      • Jitter
      • Line quality
    • Historical upload
    • Historical download

Associated revisions

Revision 22 (diff)
Added by lmurphey over 7 years ago

Finalizing the initial version of the speedtest dashboard

Reference #1696

History

#1 Updated by Luke Murphey over 7 years ago

  • Description updated (diff)

#2 Updated by Luke Murphey over 7 years ago

  • % Done changed from 0 to 30

#3 Updated by Luke Murphey over 7 years ago

  • Target version set to 0.5

#4 Updated by Luke Murphey over 7 years ago

Problems with the current design:

  • Its isn't obvious that the search running is actually the ping executing
  • The submit button sometimes runs the speedtest when the users didn't press submit
  • The historical charts don't update when the speedtest completes
  • It would be nice if the three stages (ping, upload, download performance) could happen serially so that the user gets input faster

#5 Updated by Luke Murphey over 7 years ago

Might just want to have a modal for kicking the speedtest off. This widget could show that the speedtest is running.

#6 Updated by Luke Murphey over 7 years ago

I have this working but with some caveats:

  1. The base search is not working on the results page
  2. I cannot get the parameters from the execute page to work with the search command because I cannot figure out a way to swap the search effectively between the one that gets the most recent result and the one that gets the results from the speedtest search command

#7 Updated by Luke Murphey over 7 years ago

Here is some information on the token model:

http://dev.splunk.com/view/webframework-developapps/SP-CAAAEQB

#8 Updated by Luke Murphey over 7 years ago

I wonder if it would be better just to have a search parameter runs and server tokens in the search string. Then, I could just listen for the search call and clear the runs and server parameters if the executed parameter indicates that the search has never run.

#9 Updated by Luke Murphey over 7 years ago

I also want to kick the searches on the results page to reload.

#10 Updated by Luke Murphey over 7 years ago

sourcetype="speedtest" | delta ping as jitter p=1 | eval jitter=abs(jitter) | stats max(ping) as max min(ping) as min avg(ping) as avg avg(jitter) as jitter | transpose

#11 Updated by Luke Murphey over 7 years ago

https://docs.splunk.com/Documentation/Splunk/6.5.1/ModuleRef/Splunk.util#replaceTokens.28.29

Might find an option in TokenUtils.replaceTokens() that could work.

#12 Updated by Luke Murphey over 7 years ago

TokenUtils.replaceTokens() doesn't handle all of the token processing like I was hoping. It doesn't resolve the prefix and suffixes like I was hoping.

#13 Updated by Luke Murphey over 7 years ago

Trying another technique.

In this case, I put all of the tokens in the search. Then, I have the JS set the tokens in order to get the search to run the initial time.

The only problem with this is that the search gets auto-submitted when the inputs change. I only want the search to run when the button is pressed. I tried setting searchWhenChanged="false" but the tokens still get set which causes the search to execute. Clearing the tokens also doesn't stop the search from executing.

#14 Updated by Luke Murphey over 7 years ago

  • % Done changed from 30 to 80

#15 Updated by Luke Murphey about 7 years ago

  • Status changed from New to Closed
  • % Done changed from 80 to 100

Also available in: Atom PDF