fix tiny mistakes in readmes and resources + update workflow

Author: derlin

.github/workflows/main.yml

@@ -92,6 +92,10 @@ jobs:
         with:
           path: build/libs/*.*
 
+      - name: Create info file
+        run: |
+          echo -e "ref: $GITHUB_REF \ncommit: $GITHUB_SHA\nbuild: $(date +"%Y-%m-%dT%H:%M:%SZ")" > build/libs/info.txt
+
       - name: Update nightly release
         uses: eine/tip@master
         with:

README.md

@@ -29,7 +29,7 @@ This repository is the cornerstone of BBData. It contains:
     * [Changing exposed actuators](#changing-exposed-actuators)
 - [Monitoring](#monitoring)
     * [Spring Boot Admin](#spring-boot-admin)
-    * [Prometheus + Graffana](#prometheus---graffana)
+    * [Prometheus + Grafana](#prometheus---grafana)
 
 ## Development setup
 
@@ -429,7 +429,7 @@ There are two (complementary?) supported monitoring systems:
 
 * [Spring Boot Admin](https://codecentric.github.io/spring-boot-admin/2.3.0/), 
   which lets you interact with the actuators from a UI (clear the cache, change logging levels, etc.);
-* [Prometheus](https://prometheus.io/) + [Graffana](https://grafana.com/),
+* [Prometheus](https://prometheus.io/) + [Grafana](https://grafana.com/),
   which lets you graph and monitor different metrics.
 
 ### Spring Boot Admin
@@ -457,7 +457,7 @@ spring.boot.admin.client.url=<URL OF THE ADMIN SERVER>
 spring.boot.admin.client.instance.name=BBData test Instance
 ````
 
-### Prometheus + Graffana
+### Prometheus + Grafana
 
 The BBData API ships with `io.micrometer:micrometer-registry-prometheus`. 
 If the property `management.endpoint.prometheus.enabled=true` and `prometheus` is exposed (see `management.endpoints.web.exposure.include`),

other/jmeter/local.properties

@@ -26,8 +26,8 @@ threads_about=2
 # ...for GET /objects/{id}/latest
 threads_get_latest=4
 
-# time between each request, in seconds
-period=0.1
+# sleep between each request, in milliseconds
+period=100
 # duration of the test, in seconds
 duration=180
 

other/monitoring/README.md

@@ -74,7 +74,7 @@ For all metrics of type *summary* (such as `http_server_requests_seconds_*`), we
 * `_sum`: the sum of all the records made during a time window.
     For http requests, it means the total duration of every request for each endpoint;
 
-We can work with those summaries in Prometheus/Graffana using common approaches:
+We can work with those summaries in Prometheus/Grafana using common approaches:
 
 * Average latency: `rate(timer_sum[10s])/rate(timer_count[10s])`
 * Throughput (requests per second): `rate(timer_count[10s])`

other/monitoring/config/prometheus.yml

@@ -1,7 +1,7 @@
 # my global config
 global:
-  scrape_interval:     15s # Set the scrape interval to every 15 seconds. Default is every 1 minute.
-  evaluation_interval: 15s # Evaluate rules every 15 seconds. The default is every 1 minute.
+  scrape_interval:     15s # Set the scrape interval to every [duration]. Default is every 1 minute.
+  evaluation_interval: 15s # Evaluate rules every [duration]. The default is every 1 minute.
   # scrape_timeout is set to the global default (10s).
 
 # Load rules once and periodically evaluate them according to the global 'evaluation_interval'.