Skip to content
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

Simplify logs #543

Closed
Andrii-Asiox opened this issue May 22, 2022 · 8 comments
Closed

Simplify logs #543

Andrii-Asiox opened this issue May 22, 2022 · 8 comments

Comments

@Andrii-Asiox
Copy link

Вітаю, я маю невеличку ферму телефонів на яких запущено db1000n і дуже не зручно дивитися на це простирадло логів. Чи могли б ви зробити спрощений режим де просто буде якась оцінка якості атаки, щоб було зрозуміло варто змінювати впн з'єднання чи ні. Дякую

@arriven
Copy link
Owner

arriven commented May 23, 2022

So there are couple options to achieve something similar to what you need already:

  • you can specify --log-format json and then feed those to some json parser to only gather info you need (I think https://github.com/ihorlv/db1000nX100 does something similar to that so you could take some inspiration there)
  • alternatively, you can specify --log-level fatal - that should disable all the logs except the stats table. the table may still be pretty large so if json option is not good enough I could probably make alternative reporter format that would only output total stats but not sure when I can get to it

@PerchunPak
Copy link
Contributor

Чому в документації немає нічого про ці опції?

@avoylenko
Copy link

@PerchunPak i guess in most cases it's enough to run the binary without any provided options, but you can see all of them by running the db1000n instance with '-h' argument:
./db1000n -h

@roman-kruglov
Copy link
Contributor

@arriven I'll implement it - an option to have only totals. I think it would be even better to have totals and each protocol as a target, something like:

http  | stats...
https | stats..
tcp | stats..
--------
total | stats..

Propose to call it -less-stats. Maybe fewer would be more grammatical, but I guess less is kinda more conventional for text..

@roman-kruglov
Copy link
Contributor

Maybe a numeric options would be even better? Something like -less-stats=20 would mean "show less info when the number of targets is higher than 20".

@roman-kruglov
Copy link
Contributor

Well, let's start with a simple boolean flag then #552

@roman-kruglov
Copy link
Contributor

it's merged, should be in the next release. Maybe we could close this issue now.

@arriven
Copy link
Owner

arriven commented Jun 20, 2022

available in 0.9.10, thanks to @roman-kruglov

@arriven arriven closed this as completed Jun 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants