Save process log to file

[aryan-212]

This PR fixes #2
@Matrx123

[Matrx123]

Hello Aryan, that was quick!!
one thing though, there is a problem i see with the thread implementation:
you are spawning a new thread each time on send alert and not clearing or dropping the channel which will results in memory leak at some point.
maybe you can create the drop trait to properly close the channel and stop the thread, you can also create a thread at once, and in network monitor (tokio implementation) we used unbounded channel, so here on thread you can use try_send() to send to avoid blocking.

i like your idea to keep the buffer size and write in batches, but we can also clear flush it after it fills , its a small number so you can use usize in place of i32.

i am just thinking out loud here, open for discussions!!
cheers 🥳

[aryan-212]

Hello Aryan, that was quick!! one thing though, there is a problem i see with the thread implementation: you are spawning a new thread each time on send alert and not clearing or dropping the channel which will results in memory leak at some point. maybe you can create the drop trait to properly close the channel and stop the thread, you can also create a thread at once, and in network monitor (tokio implementation) we used unbounded channel, so here on thread you can use try_send() to send to avoid blocking.

i like your idea to keep the buffer size and write in batches, but we can also clear flush it after it fills , its a small number so you can use usize in place of i32.

i am just thinking out loud here, open for discussions!! cheers 🥳

Hi, thanks for figuring that out, totally forgot the joining of threads 😅

[Matrx123]

Hello aryan,
please share the sshot of logs as well from your local environment in the discussions tab for future refrences.
Thanks for the PR though, i will review and merge.

Cheers!! 🥳

[aryan-212]

Here ! @Matrx123