about summary refs log tree commit diff
diff options
context:
space:
mode:
authorllzmb <46303940+llzmb@users.noreply.github.com>2021-09-10 14:26:51 +0200
committerGitHub <noreply@github.com>2021-09-10 14:26:51 +0200
commit6546a0a5fd5532464916c6c4adfbb22d87a5acd5 (patch)
treeebdc6d22fe6bc22bf80361794dd4f6357ef45009
parent78d7944bbf4608437563114c0e4291a9a516cfff (diff)
downloadafl++-6546a0a5fd5532464916c6c4adfbb22d87a5acd5.tar.gz
Update docs/rpc_statsd.md
-rw-r--r--docs/rpc_statsd.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/rpc_statsd.md b/docs/rpc_statsd.md
index 2d340dd7..288d56cb 100644
--- a/docs/rpc_statsd.md
+++ b/docs/rpc_statsd.md
@@ -62,7 +62,7 @@ The easiest way to install and set up the infrastructure is with Docker and Dock
 
 Depending on your fuzzing setup and infrastructure, you may not want to run these applications on your fuzzer instances. This setup may be modified before use in a production environment; for example, adding passwords, creating volumes for storage, tweaking the metrics gathering to get host metrics (CPU, RAM, and so on).
 
-For all your fuzzers, only one instance of StatsD, Prometheus, and Grafana is required.
+For all your fuzzing instances, only one instance of Prometheus and Grafana is required. The [statsd exporter](https://registry.hub.docker.com/r/prom/statsd-exporter) converts the StatsD metrics to Prometheus. If you are using a provider that supports StatsD directly, you can skip this part of the setup."
 
 You can create and move the infrastructure files into a directory of your choice. The directory will store all the required configuration files.