You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not really a core-feature here, but I think it would be nice to have a proper way to directly create statistics from logentries, like how many clients per timeframe or connected time per client / average and so on. At the end of the day it's these numbers which represent the fun in hosting a service like this :-)
Maybe this is somewhat out of scope, but maybe easier would be an additional log-entry at info-level after a client has disconnected including a consecutive ID like so:
# date time loglv service id ip port state/notice
2021-03-24 16:26:23 INFO TarpitServer: Client (4567, '1.2.3.4', 60216) connected
2021-03-24 16:36:31 INFO TarpitServer: Client (4567, '1.2.3.4', 60216) disconnected
2021-03-24 16:36:31 INFO TarpitServer: Client (4567, '1.2.3.4', 60216) duration: 608s (...or human readable)
cheers,
zeus
The text was updated successfully, but these errors were encountered:
Uhm, yes, did not look at this. You're right. The primary goal would be to be able to parse logs and generate statistics from it, the precise way would not matter that much (anyways, I think a summarized time as well as an assigned ID/reference/hash in the log-message would make this alot easier xD ).
Not really a core-feature here, but I think it would be nice to have a proper way to directly create statistics from logentries, like how many clients per timeframe or connected time per client / average and so on. At the end of the day it's these numbers which represent the fun in hosting a service like this :-)
Maybe this is somewhat out of scope, but maybe easier would be an additional log-entry at info-level after a client has disconnected including a consecutive ID like so:
cheers,
zeus
The text was updated successfully, but these errors were encountered: