Project

General

Profile

Feature #1731

Speedtest modular input

Added by Luke Murphey almost 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Luke Murphey
Target version:
1.0
Start date:
02/06/2017
Due date:
% Done:

100%

Related issues

Related to Network Tools - Feature #1790: Add support for cron scheduling to modular input base class Rejected 03/17/2017

Associated revisions

Revision 163 (diff)
Added by lukemurphey over 7 years ago

Adding ability to do speedtest via a modular input

Reference #1731

History

#2 Updated by Luke Murphey over 7 years ago

  • Subject changed from Speedtest modular alert to Speedtest modular input

#3 Updated by Luke Murphey over 7 years ago

  • Blocked by Feature #1790: Add support for cron scheduling to modular input base class added

#4 Updated by Luke Murphey over 7 years ago

  • Assignee set to Luke Murphey

I could just ship with a scripted input. The only issue with this is that it cannot easily take the arguments and I need these arguments to change the way that the stash parsing works. I also would like the script to use the global index setting if possible.

#5 Updated by Luke Murphey over 7 years ago

I could make this run in multi instance mode which would get me the ability to use a cron schedule.

#6 Updated by Luke Murphey over 7 years ago

  • Target version changed from 0.8 to 0.10

#7 Updated by Luke Murphey over 7 years ago

  • Blocked by deleted (Feature #1790: Add support for cron scheduling to modular input base class)

#8 Updated by Luke Murphey over 7 years ago

  • Related to Feature #1790: Add support for cron scheduling to modular input base class added

#9 Updated by Luke Murphey over 7 years ago

  • Target version changed from 0.10 to 1.0

#10 Updated by Luke Murphey over 7 years ago

I have this made but the cron scheduling isn't working. Splunk isn't executing the input.

See https://answers.splunk.com/answers/445001/rest-modular-input-cron-schedule-not-working-known.html

#12 Updated by Luke Murphey over 7 years ago

According to https://docs.splunk.com/Documentation/Splunk/6.5.3/Admin/Inputsconf#inputs.conf.spec

interval = [<number>|<cron schedule>]
* How often to run the specified command (in seconds), or a valid cron
  schedule.
* NOTE: when you specify a cron schedule, the input does not run the
  script on start-up.
* If you specify the interval as a number, it may have a fractional
  component; e.g., 3.14
* The cron implementation for data inputs does not currently support names
  of months or days.
* Defaults to 60.0 seconds.
* The special value 0 forces this scripted input to be run continuously;
  that is, as soon as the script exits, the input restarts it.
* The special value -1 causes the scripted input to run once on start-up.

#13 Updated by Luke Murphey over 7 years ago

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

Also available in: Atom PDF