luzifer/continuous-spark
1
0
Fork 0
mirror of https://github.com/Luzifer/continuous-spark.git synced 2024-10-18 04:44:24 +00:00
Code Issues Releases Wiki Activity
Daemon intended to do continuous tests against a sparkyfish server
24 commits 3 branches 5 tags 1.5 MiB
Go 99.3%
Makefile 0.7%
Find a file
dependabot[bot] eedfe435b7
Bump golang.org/x/crypto from 0.0.0-20201124201722-c8d3bf9c5392 to 0.1.0 
Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.0.0-20201124201722-c8d3bf9c5392 to 0.1.0.
- [Release notes](https://github.com/golang/crypto/releases)
- [Commits](https://github.com/golang/crypto/commits/v0.1.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
2023-02-25 00:56:23 +00:00
.gitignore Keep a local log of all measures 2017-07-28 07:13:51 +02:00
.repo-runner.yaml Update reporunner image 2019-01-27 15:29:48 +01:00
go.mod Bump golang.org/x/crypto from 0.0.0-20201124201722-c8d3bf9c5392 to 0.1.0 2023-02-25 00:56:23 +00:00
go.sum Bump golang.org/x/crypto from 0.0.0-20201124201722-c8d3bf9c5392 to 0.1.0 2023-02-25 00:56:23 +00:00
History.md prepare release v1.0.3 2021-01-10 15:57:31 +01:00
influx.go Lint: Fix linter errors, improve error handling 2019-01-27 15:48:43 +01:00
LICENSE Fix LICENSE file 2019-01-27 15:30:01 +01:00
main.go Add source interface selection 2021-03-06 17:42:38 +01:00
Makefile Add automated building 2017-07-28 07:23:09 +02:00
ping.go Lint: Fix linter errors, improve error handling 2019-01-27 15:48:43 +01:00
README.md Breaking: Code cleanup, switch to InfluxDB for graphing 2019-01-27 15:25:13 +01:00
screenshot.png Add README 2017-07-28 07:22:15 +02:00
spark.go Add source interface selection 2021-03-06 17:42:38 +01:00
throughput.go Lint: Fix linter errors, improve error handling 2019-01-27 15:48:43 +01:00

README.md

Go Report Card

Luzifer / continuous-spark

This tool is a daemon intended to do continuous tests against a sparkyfish server. The measurements are sent to an InfluxDB for graphing and are stored locally in a TSV file for reference.

Why? Quite easy: My internet connection is quite often way slower (170Kbit vs. 200Mbit) as promised in the contract I'm paying for so I set up this daemon on my NAS connected using 2x1Gbit cable to my providers FritzBox. On the other side an unmodified sparkyfish server is running on a 1Gbit datacenter connection. The test is executed every 15m and looking at the graph causes me to weep...