fix rpc_stats.md

docs/Changelog.md

@@ -48,6 +48,8 @@ sending a mail to <afl-users+subscribe@googlegroups.com>.
   - added dummy Makefile to instrumentation/
   - Updated utils/afl_frida to be 5% faster
   - Added AFL_KILL_SIGNAL env variable (thanks @v-p-b)
+  - @Edznux added a nice documentation on how to use rpc.statsd with
+    afl++ in docs/rpc_statsd.md, thanks!
 
 ### Version ++3.00c (release)
   - llvm_mode/ and gcc_plugin/ moved to instrumentation/

docs/rpc_statsd.md

@@ -31,9 +31,9 @@ By doing so, you might be able to see when the fuzzing process has reached a sta
 (according to your own criteria) for your targets, etc. And doing so without requiring to log into each instance manually.
 
 An example visualisation may look like the following:
-![StatsD Grafana](./visualization/StatsD-grafana.png)
+![StatsD Grafana](visualization/statsd-grafana.png)
 
-*Notes: The exact same dashboard can be imported with [this JSON template](./statsd/grafana-afl++.json).*
+*Notes: The exact same dashboard can be imported with [this JSON template](statsd/grafana-afl++.json).*
 
 ## How to use
 
@@ -140,4 +140,4 @@ AFL_STATSD_TAGS_FLAVOR=dogstatsd AFL_STATSD=1 afl-fuzz -S test-fuzzer-2 -i i -o
 ```
 
 This setup may be modified before use in production environment. Depending on your needs: addind passwords, creating volumes for storage,
-tweaking the metrics gathering to get host metrics (CPU, RAM ...).
+tweaking the metrics gathering to get host metrics (CPU, RAM ...).