-
-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Counterpart of afl++'s rpc_statsd? #2895
Comments
Interesting, I don't personally use either statsd nor prometheus. TL;DR: I don't think we have that right now. |
Thank you for your reply:) And yet there is another question: can we have two or more monitors at the same time? The tui monitor and the to-be-implemented statsd monitor should both be there in my experience. We could look at the statsd monitor for the overall-information of all fuzzing instances we are running, and look at the individual tui monitor for detail information. |
You could build a simple monitor that takes two child monitors and forwards every incoming message to both. |
I wonder if there is a counterpart of afl++'s rpc_statsd in LibAFL? I noted there is a prometheus monitor, but as far as I understand, this is not what I want.
The afl++'s rpc statsd has the following abilities:
Currently, the prometheus monitor is not good for incremental fuzzing, i.e., there may be several new targets to be fuzzed every day, so I want to add those stats as well. However, in current solution, each fuzzing instance needs a separate port, and we need to aggregate stats from all ports to show a total information.
The text was updated successfully, but these errors were encountered: