Add StatsD monitor #2969

Evian-Zhang · 2025-02-12T11:45:32Z

This PR adds a StatsdMonitor, which is roughly a counterpart of AFL++'s rpc_statsd.

There are two more things could be done after this PR:

Write sections in LibAFL book to tell about how to use statsd metrics in LibAFL (or we could even tell about all other monitors' usage in that section)
As you could see in libafl/src/monitors/statsd.rs, there are several metrics currently not available, which is available in AFL++. Some of these metrics could be resolved in AflStatsStage. This stage involves much with the Monitor's statistics, so we should think more about this (and maybe some refactors to make this more maintainable). (In my first thought, shouldn't it be Monitor's responsibility to write to fuzzer_stats and plot_data?)

This PR also solves #2895.

libafl/src/monitors/mod.rs

libafl/src/monitors/stats/mod.rs

libafl/src/monitors/statsd.rs

libafl/src/monitors/tui/mod.rs

domenukk · 2025-02-12T13:14:06Z

Nice!

Do we still want to keep the prometheus monitor, then? Don't they solve similar problems?

Evian-Zhang · 2025-02-12T13:35:44Z

In my understanding, prometheus monitor is used to view detailed statistics about one fuzzing instance (with multiple clients maybe), since it can show the statistics about individual clients.

The statsd is used to view aggregated statistics about multiple fuzzing instances (showing individual client statistics will make the visualized graph very distracting).

Evian-Zhang · 2025-02-12T23:01:34Z

Are there any conversations not resolved? Should we merge this PR?

domenukk · 2025-02-13T00:15:30Z

Thank you!

domenukk · 2025-02-13T00:16:11Z

libafl/src/monitors/stats/manager.rs

@@ -206,6 +206,7 @@ impl ClientStatsManager {
    }

    /// Get item geometry
+    #[allow(clippy::cast_precision_loss)]


Ah, this should be expect

I will create a PR quickly

Add StatsD monitor

f8374cf