From 9063002af22e916701588248eca2fd2669e4d0df Mon Sep 17 00:00:00 2001
From: vanhauser-thc <vh@thc.org>
Date: Thu, 9 Dec 2021 13:22:10 +0100
Subject: rename path

---
 docs/rpc_statsd.md | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

(limited to 'docs/rpc_statsd.md')

diff --git a/docs/rpc_statsd.md b/docs/rpc_statsd.md
index 003b9c79..d8f0fb67 100644
--- a/docs/rpc_statsd.md
+++ b/docs/rpc_statsd.md
@@ -26,7 +26,7 @@ StatsD allows you to receive and aggregate metrics from a wide range of
 applications and retransmit them to a backend of your choice.
 
 From AFL++, StatsD can receive the following metrics:
-- cur_path
+- cur_item
 - cycle_done
 - cycles_wo_finds
 - edges_found
@@ -34,18 +34,18 @@ From AFL++, StatsD can receive the following metrics:
 - execs_per_sec
 - havoc_expansion
 - max_depth
-- paths_favored
-- paths_found
-- paths_imported
-- paths_total
+- corpus_favored
+- corpus_found
+- corpus_imported
+- corpus_count
 - pending_favs
 - pending_total
 - slowest_exec_ms
 - total_crashes
-- unique_crashes
-- unique_hangs
+- saved_crashes
+- saved_hangs
 - var_byte_count
-- variable_paths
+- corpus_variable
 
 Depending on your StatsD server, you will be able to monitor, trigger alerts, or
 perform actions based on these metrics (for example: alert on slow exec/s for a
-- 
cgit 1.4.1