csv output

[thetechfirm]

not sure if i just missed it but I cant find the option to save the output to a CSV format.
if its not there, that feature would be helpful for me.

regards

[pouriyajamshidi]

Hi @thetechfirm,

There is no option to output in CSV format yet.

We will see if someone is willing to take this up.

[thetechfirm]

I'm a casual coder but not familiar with go, otherwise I would give it a try Fyi. I wrote a quick k post and video for networkdatapedia.com Oct 9 or 11

…

On October 6, 2024 12:28:08 PM EDT, Pouriya Jamshidi ***@***.***> wrote: Hi @thetechfirm, There is no option to output in CSV format yet. We will see if someone is willing to take this up. -- Reply to this email directly or view it on GitHub: #240 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[pouriyajamshidi]

Nice to know about the post!

no worries, probably someone will pick it up if I cannot manage to get to it myself. Life is very busy these days

[thetechfirm]

I totally understand and , my pleasure regarding the post From: Pouriya Jamshidi ***@***.***> Sent: Sunday, October 6, 2024 1:50 PM To: pouriyajamshidi/tcping ***@***.***> Cc: thetechfirm ***@***.***>; Mention ***@***.***> Subject: Re: [pouriyajamshidi/tcping] csv output (Issue #240) Nice to know about the post! no worries, probably someone will pick it up if I cannot manage to get to it myself. Life is very busy these days — Reply to this email directly, view it on GitHub <#240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXNNNQCKORMGKQCUNECE6TZ2FZ4FAVCNFSM6AAAAABPOKQ35GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJVGUZDGNZUHA> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ALXNNNSTP3LV5NB4DFDSEXLZ2FZ4FA5CNFSM6AAAAABPOKQ35GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUOZDFKI.gif> Message ID: ***@***.*** ***@***.***> >

[SYSHIL]

Hii @pouriyajamshidi Shall I pick this up?

[pouriyajamshidi]

Hi @SYSHIL,

Hope you are well.

Sure, please go ahead.

[SYSHIL]

I'm doing good @pouriyajamshidi, hope you are too :)

There is no option to output in CSV format yet.

We can either treat this as a separate printer like our DB printer or JSON printer or we let this saveToCSV option co-exist with the existing behaviour. in my opinion a separate printer looks neater what do you think?

[pouriyajamshidi]

I'm doing good @pouriyajamshidi, hope you are too :)

There is no option to output in CSV format yet.

We can either treat this as a separate printer like our DB printer or JSON printer or we let this saveToCSV option co-exist with the existing behaviour. in my opinion a separate printer looks neater what do you think?

I am also doing fine man, thank you.

yes, a separate printer sounds more logical.

[thetechfirm]

I agree From: Syed Shahidh Ilhan F ***@***.***> Sent: Sunday, October 20, 2024 3:18 AM To: pouriyajamshidi/tcping ***@***.***> Cc: thetechfirm ***@***.***>; Mention ***@***.***> Subject: Re: [pouriyajamshidi/tcping] csv output (Issue #240) I'm doing good @pouriyajamshidi <https://github.com/pouriyajamshidi> , hope you are too :) There is no option to output in CSV format yet. I think a savetoCSV option which records the csv output in a file sounds more useful than spitting out the terminal output in CSV format. Just wanted to clarify this before proceeding — Reply to this email directly, view it on GitHub <#240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXNNNQNGV4AD3KGXWABCQTZ4NKIZAVCNFSM6AAAAABPOKQ35GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGY4TENBQG4> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ALXNNNTR4ZZSNUYDG3PQDV3Z4NKIZA5CNFSM6AAAAABPOKQ35GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUQQXPLO.gif> Message ID: ***@***.*** ***@***.***> >

[thetechfirm]

I was just thinking, maybe the CSV file can have the date, time, target ip, port, and time Then then provide the final stats at the bottom. Much like the current output I’m not a full time coder , so I would be happy with pretty well anything. regards From: Syed Shahidh Ilhan F ***@***.***> Sent: Sunday, October 20, 2024 3:18 AM To: pouriyajamshidi/tcping ***@***.***> Cc: thetechfirm ***@***.***>; Mention ***@***.***> Subject: Re: [pouriyajamshidi/tcping] csv output (Issue #240) I'm doing good @pouriyajamshidi <https://github.com/pouriyajamshidi> , hope you are too :) There is no option to output in CSV format yet. I think a savetoCSV option which records the csv output in a file sounds more useful than spitting out the terminal output in CSV format. Just wanted to clarify this before proceeding — Reply to this email directly, view it on GitHub <#240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXNNNQNGV4AD3KGXWABCQTZ4NKIZAVCNFSM6AAAAABPOKQ35GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMRUGY4TENBQG4> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ALXNNNTR4ZZSNUYDG3PQDV3Z4NKIZA5CNFSM6AAAAABPOKQ35GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUQQXPLO.gif> Message ID: ***@***.*** ***@***.***> >

[SYSHIL]

Hi @thetechfirm
I have a question...how do you think we should handle statistics output we now get in the terminal while working with csv files?

I see two options,

1. We pipe the statistics output to a separate csv file with a different schema compared to the csv file we'll send our terminal output to
2. Ignore printing statistics in we're recording the output in csv format.

I'm leaning towards option 2 but I would love to hear your thoughts on this :)

[thetechfirm]

I agree. I like option 2 as well I appreciate the email. Cheers From: Syed Shahidh Ilhan F ***@***.***> Sent: Tuesday, November 26, 2024 2:46 PM To: pouriyajamshidi/tcping ***@***.***> Cc: thetechfirm ***@***.***>; Mention ***@***.***> Subject: Re: [pouriyajamshidi/tcping] csv output (Issue #240) Hi @thetechfirm <https://github.com/thetechfirm> I have a question...how do you think we should handle statistics output we now get in the terminal while working with csv files? I see two options, 1. We pipe the statistics output to a separate csv file with a different schema compared to the csv file we'll send our terminal output to 2. Ignore printing statistics in we're recording the output in csv format. I'm leaning towards option 2 but I would love to hear your thoughts on this :) — Reply to this email directly, view it on GitHub <#240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXNNNRA3DJ333BRVZXOQL32CTFWXAVCNFSM6AAAAABPOKQ35GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBRG44DKNJWGM> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ALXNNNVPAOHYO66TFNGDLAT2CTFWXA5CNFSM6AAAAABPOKQ35GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUVDY35W.gif> Message ID: ***@***.*** ***@***.***> >

[pouriyajamshidi]

Hey @thetechfirm, Good news!

The CSV PR is merged now.

I am planning to have a release by mid Jan after some minor changes to the code base (not necessarily CSV related).

Another option (--no-color) next to CSV output is also added which you can benefit from while redirecting output to a file. This way the ANSI control characters will not be written in the file.

Of course, if you are an early adopter, feel free to compile from source and use it like that till the official release.

[thetechfirm]

Awesome I will wait for the release since I have a pretty busy schedule for the next little while Thanks for the email and merry Christmas to you and your family From: Pouriya Jamshidi ***@***.***> Sent: Monday, December 23, 2024 5:48 AM To: pouriyajamshidi/tcping ***@***.***> Cc: thetechfirm ***@***.***>; Mention ***@***.***> Subject: Re: [pouriyajamshidi/tcping] csv output (Issue #240) Hey @thetechfirm <https://github.com/thetechfirm> , Good news! The CSV PR is merged now. I am planning to have a release by mid Jan after some minor changes to the code base (not necessarily CSV related). Another option (--no-color) next to CSV output is also added which you can benefit from while redirecting output to a file. This way the ANSI control characters will not be written in the file. Of course, if you are an early adopter, feel free to compile from source and use it like that till the official release. — Reply to this email directly, view it on GitHub <#240 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALXNNNS6QR3DVMNVV4PRI432G7S6ZAVCNFSM6AAAAABPOKQ35GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNJZGQZDOOJSGY> . You are receiving this because you were mentioned. <https://github.com/notifications/beacon/ALXNNNWJLD2IO4NUDV5CQAT2G7S6ZA5CNFSM6AAAAABPOKQ35GWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUYRXCVM.gif> Message ID: ***@***.*** ***@***.***> >

[pouriyajamshidi]

Thank you so much, @thetechfirm

Merry Christmas to you and your family too!