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
Need some input for my gui app #69
Comments
There is an experiential library feature in nethogs Basic use:
Here is an experimental GUI I made using the lib: https://github.com/mbfoss/gnethogs |
@akshaykmr that looks pretty amazing! I agree nethogs' output is currently not very nicely machine-consumable. Indeed a JSON stdout stream feature might be a nice addition, though it might not be suitable for all use cases. |
I want to use I have defined the following fields following the class NethogsMonitorRecord(ctypes.Structure):
_fields_ = [
('record_id', ctypes.c_int),
('name', ctypes.c_char_p),
('pid', ctypes.c_int),
('uid', ctypes.c_uint),
('device_name', ctypes.c_char_p),
('sent_bytes', ctypes.c_ulonglong),
('recv_bytes', ctypes.c_ulonglong),
('sent_kbs', ctypes.c_float),
('recv_kbs', ctypes.c_float)] If I print everything in this class I'm getting strange values: EDIT: It is working fine not, i had to add argtypes and use a pointer |
Edit: here is the repository
Hey there I am currently making a gui app using nethogs at the backend. The idea is to run a light server and use a webview for the desktop app. This way output can also be viewed from the network on a different machine. here are some screenshots
The per process graph can also be seen by selecting the process from the list
The app is still in very early stages and not released yet but some input would be appreciated.
I am using the nethogs trace mode as data source but the data is not clean as I would like (long process path/ IP adresses etc.) I would appreciate if trace mode listed pid, user device as well, more preferably in a JSON format such that any future changes/additions do not break dependent apps(currently I am parsing output line by line column-wise).
The text was updated successfully, but these errors were encountered: