fix doc

Readme.md

@@ -53,21 +53,27 @@ have fun!
 
 show pro/con overview:
 
-**prometheus:**
+### prometheus
-* + you get nicer graphs with counters and bars if you ask me
+
-* + you can use alertmanager if you want advanced alerting
+pro
-* + optimized for timeseries data
+* you get nicer graphs with counters and bars if you ask me
-* - not designed for keeping long timeseries (weeks or some months are fine)
+* you can use alertmanager if you want advanced alerting
-* - not possible to import historical data
+* optimized for timeseries data
-* - not as flexible as mysql regarding complex queries
+con
-
+* not designed for keeping long timeseries (weeks or some months are fine)
-**mysql**:
+* not possible to import historical data
-* + you can import your ALL.txt since 2019
+* not as flexible as mysql regarding complex queries
-* + you can store a lot of data over a long timeframe
+
-* + you can propably build more complex queries in sql
+### mysql
-* - in comparison to prometheus not optimized for timeseries, but still good enough
+
-* - gauge based graphs are not as nice as counter/bars if you ask me
+pro:
-* - you can use *only* graphanas internal alerting
+* you can import your ALL.txt since 2019
+* you can store a lot of data over a long timeframe
+* you can propably build more complex queries in sql
+con:
+* in comparison to prometheus not optimized for timeseries, but still good enough
+* gauge based graphs are not as nice as counter/bars if you ask me
+* you can use *only* graphanas internal alerting
 
 both allow distributed setups with multiple wsjtx instances submitting their data to a central prometheus or mysql service.
 you can as well run both in parallel and use prometheus for a live overview and mysql for historical evaluations.
@@ -110,7 +116,7 @@ choose a bigger interval
 ### how long does it take to import my data into mysql?
 
 * my ALL.TXT (new format start july 2019) contains ~ 13.7 mio lines and has ~ 850M
-* converting to csv takes ~ 14min on i7-4750HQ (2015) and the result has ~ 1.2G
+* converting to csv takes ~ 12min on i7-4750HQ (2015) and the result has ~ 1.2G
  * currently this is done using another module which uses regular expressions which is not optimial for this use case
 * importing the csv to mysql takes ~ 3.5min
 * querying the whole time (~ 1.5 years) in grafana takes some seconds

todo.md

@@ -22,8 +22,8 @@
   * kontrolle sollte beim db admin liegen
 
 * doc
-** german docs..
+  * german docs..
-** server und/oder skript/readme
+  * server und/oder skript/readme
 
 * fix dashboards
   * umgang mit refresh der variablen??