Re: Babeltrace Patch

Re: Babeltrace Patch

[Mohamad Gebai]

[-- Attachment #1.1: Type: text/plain, Size: 1525 bytes --]

Hi Nesrine,

You can use LTTng to send your traces over the network. See
https://lttng.org/docs/v2.10/#doc-sending-trace-data-over-the-network

Mohamad


On 04/11/2018 08:11 AM, Nesrine Zouari wrote:
> Hello,
>
> I am computer engineering student and I am actually working on my
> graduation project which is about Qemu Trace. 
>
> In this project, Qemu is considered as a user-space instrumented
> application. 
>
> I have used:
>
> 1) LTTng-Tools to control Qemu trace. 
>
> 2) Babeltrace to convert the CTF traces to a human readable text.
>
> Now, I aim to develop a patch to the Babeltrace. Instead of printing
> the traces on the console or in a file, I would like to send the
> traces over TCP/IP to a third-party tool for processing.
> My third-party tool is installed on a windows machine. For this
> reason, the use of LTTng relay daemon will not be a good solution.
>
> My question is the following:
>
> To which file (of the Babeltrace source code) should I make changes to
> answer my use case?
>
> Best regards,
>
> -----------------------------------------------------------------------------------------
>
> Nesrine ZOUARI
> Computer Engineering Student 
> Department of Computer Engineering and Applied Mathematics
> National Engineering School of Sfax (ENIS)
> University of Sfax-Tunisia
> Tel: +216 52 620 475
>
>
> ‌
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


[-- Attachment #1.2: Type: text/html, Size: 18625 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Babeltrace Patch

[Nesrine Zouari]

[-- Attachment #1.1: Type: text/plain, Size: 2242 bytes --]

Thank you for your response.

I have already tested lttng-relayd on a Linux remote machine and it had
worked. But the problem is that my remote machine is WINDOWS so I don't
think that I can run lttng-relayd on it.
Is there a solution to run lttng-relayd on Windows??


‌

On Wed, Apr 11, 2018 at 3:41 PM, Mohamad Gebai <mgebai@suse.de> wrote:

> Hi Nesrine,
>
> You can use LTTng to send your traces over the network. See
> https://lttng.org/docs/v2.10/#doc-sending-trace-data-over-the-network
>
> Mohamad
>
>
>
> On 04/11/2018 08:11 AM, Nesrine Zouari wrote:
>
> Hello,
>
> I am computer engineering student and I am actually working on my
> graduation project which is about Qemu Trace.
>
> In this project, Qemu is considered as a user-space instrumented
> application.
>
> I have used:
>
> 1) LTTng-Tools to control Qemu trace.
>
> 2) Babeltrace to convert the CTF traces to a human readable text.
>
> Now, I aim to develop a patch to the Babeltrace. Instead of printing the
> traces on the console or in a file, I would like to send the traces over
> TCP/IP to a third-party tool for processing.
> My third-party tool is installed on a windows machine. For this reason,
> the use of LTTng relay daemon will not be a good solution.
>
> My question is the following:
>
> To which file (of the Babeltrace source code) should I make changes to
> answer my use case?
>
> Best regards,
>
> ------------------------------------------------------------
> -----------------------------
>
> Nesrine ZOUARI
> Computer Engineering Student
> Department of Computer Engineering and Applied Mathematics
> National Engineering School of Sfax (ENIS)
> University of Sfax-Tunisia
> Tel: +216 52 620 475
>
>
> ‌
>
>
> _______________________________________________
> lttng-dev mailing listlttng-dev@lists.lttng.orghttps://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>


-- 
-----------------------------------------------------------------------------------------

Nesrine ZOUARI
Computer Engineering Student
Department of Computer Engineering and Applied Mathematics
National Engineering School of Sfax (ENIS)
University of Sfax-Tunisia
Tel: +216 52 620 475

[-- Attachment #1.2: Type: text/html, Size: 22007 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Babeltrace Patch

[Mohamad Gebai]

[-- Attachment #1.1: Type: text/plain, Size: 2043 bytes --]

Sorry, I just realized that you said using the relayd is not an option.
I'd let one of the Babeltrace experts answer your question, but I think
it might be a challenge. What's your use case? Do you need the trace
sent in "real-time"?

Mohamad


On 04/11/2018 10:41 AM, Mohamad Gebai wrote:
> Hi Nesrine,
>
> You can use LTTng to send your traces over the network. See
> https://lttng.org/docs/v2.10/#doc-sending-trace-data-over-the-network
>
> Mohamad
>
>
> On 04/11/2018 08:11 AM, Nesrine Zouari wrote:
>> Hello,
>>
>> I am computer engineering student and I am actually working on my
>> graduation project which is about Qemu Trace. 
>>
>> In this project, Qemu is considered as a user-space instrumented
>> application. 
>>
>> I have used:
>>
>> 1) LTTng-Tools to control Qemu trace. 
>>
>> 2) Babeltrace to convert the CTF traces to a human readable text.
>>
>> Now, I aim to develop a patch to the Babeltrace. Instead of printing
>> the traces on the console or in a file, I would like to send the
>> traces over TCP/IP to a third-party tool for processing.
>> My third-party tool is installed on a windows machine. For this
>> reason, the use of LTTng relay daemon will not be a good solution.
>>
>> My question is the following:
>>
>> To which file (of the Babeltrace source code) should I make changes
>> to answer my use case?
>>
>> Best regards,
>>
>> -----------------------------------------------------------------------------------------
>>
>> Nesrine ZOUARI
>> Computer Engineering Student 
>> Department of Computer Engineering and Applied Mathematics
>> National Engineering School of Sfax (ENIS)
>> University of Sfax-Tunisia
>> Tel: +216 52 620 475
>>
>>
>> ‌
>>
>>
>> _______________________________________________
>> lttng-dev mailing list
>> lttng-dev@lists.lttng.org
>> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


[-- Attachment #1.2: Type: text/html, Size: 20116 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Babeltrace Patch

[Geneviève Bastien]

[-- Attachment #1.1: Type: text/plain, Size: 1935 bytes --]

Hi Nesrine,


I don't know about babeltrace over TCP/IP. But there are tools to read
lttng traces on Windows: Trace Compass [1] can read and analyse a trace
with all kind of data driven analyzes. It can also control a tracing
session [2] and bring the trace on your windows machine. There's also
lttng-scope that reads CTF traces on Windows [3].

[1] http://tracecompass.org
[2]
http://archive.eclipse.org/tracecompass/doc/stable/org.eclipse.tracecompass.doc.user/LTTng-Tracer-Control.html#LTTng_Tracer_Control
[3] https://lttng.org/beta/

Cheers,

Geneviève




On 2018-04-11 08:11 AM, Nesrine Zouari wrote:
> Hello,
>
> I am computer engineering student and I am actually working on my
> graduation project which is about Qemu Trace. 
>
> In this project, Qemu is considered as a user-space instrumented
> application. 
>
> I have used:
>
> 1) LTTng-Tools to control Qemu trace. 
>
> 2) Babeltrace to convert the CTF traces to a human readable text.
>
> Now, I aim to develop a patch to the Babeltrace. Instead of printing
> the traces on the console or in a file, I would like to send the
> traces over TCP/IP to a third-party tool for processing.
> My third-party tool is installed on a windows machine. For this
> reason, the use of LTTng relay daemon will not be a good solution.
>
> My question is the following:
>
> To which file (of the Babeltrace source code) should I make changes to
> answer my use case?
>
> Best regards,
>
> -----------------------------------------------------------------------------------------
>
> Nesrine ZOUARI
> Computer Engineering Student 
> Department of Computer Engineering and Applied Mathematics
> National Engineering School of Sfax (ENIS)
> University of Sfax-Tunisia
> Tel: +216 52 620 475
>
>
> ‌
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev


[-- Attachment #1.2: Type: text/html, Size: 19336 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Babeltrace Patch

[Nesrine Zouari]

[-- Attachment #1.1: Type: text/plain, Size: 3890 bytes --]

Thank you for your response Geneviève.

I have already tried Tracecompass and lttng-scope and they match exactly my
project use case.

But as I said in the beginning, I am working on my *graduation project* and
I have to develop *client/server applications communicating through TCP
socket (in C language).*

This is a short description of my project requirements:
My project is divided into two parts:

*      1)* Collecting traces from Qemu (It is already an instrumented user
space application).

*       2)* Sending the collected traces to a third-party tool for analysis.

* Qemu, LTTng demons and my server application are running on the same
Linux machine.

* The client application is running on a remote WINDOWS machine.
   Client is able now to control the trace remotely (start and stop) and
get the trace collected in a text file.


*This is what I am trying to do right now:*

Instead of writing the traces to a text file, I would like to send those
traces over TCP to my client application.
So I think that the problem now is* how to make Babeltrace convert CTF
traces and send them to my client application through TCP.*

I would be grateful if you will give me some hints or another idea to
satisfy my project requirements.

Best regards,


‌

On Wed, Apr 11, 2018 at 4:37 PM, Geneviève Bastien <gbastien@versatic.net>
wrote:

> Hi Nesrine,
>
>
> I don't know about babeltrace over TCP/IP. But there are tools to read
> lttng traces on Windows: Trace Compass [1] can read and analyse a trace
> with all kind of data driven analyzes. It can also control a tracing
> session [2] and bring the trace on your windows machine. There's also
> lttng-scope that reads CTF traces on Windows [3].
>
> [1] http://tracecompass.org
> [2] http://archive.eclipse.org/tracecompass/doc/stable/org.
> eclipse.tracecompass.doc.user/LTTng-Tracer-Control.html#
> LTTng_Tracer_Control
> [3] https://lttng.org/beta/
>
> Cheers,
>
> Geneviève
>
>
>
> On 2018-04-11 08:11 AM, Nesrine Zouari wrote:
>
> Hello,
>
> I am computer engineering student and I am actually working on my
> graduation project which is about Qemu Trace.
>
> In this project, Qemu is considered as a user-space instrumented
> application.
>
> I have used:
>
> 1) LTTng-Tools to control Qemu trace.
>
> 2) Babeltrace to convert the CTF traces to a human readable text.
>
> Now, I aim to develop a patch to the Babeltrace. Instead of printing the
> traces on the console or in a file, I would like to send the traces over
> TCP/IP to a third-party tool for processing.
> My third-party tool is installed on a windows machine. For this reason,
> the use of LTTng relay daemon will not be a good solution.
>
> My question is the following:
>
> To which file (of the Babeltrace source code) should I make changes to
> answer my use case?
>
> Best regards,
>
> ------------------------------------------------------------
> -----------------------------
>
> Nesrine ZOUARI
> Computer Engineering Student
> Department of Computer Engineering and Applied Mathematics
> National Engineering School of Sfax (ENIS)
> University of Sfax-Tunisia
> Tel: +216 52 620 475
>
>
> ‌
>
>
> _______________________________________________
> lttng-dev mailing listlttng-dev@lists.lttng.orghttps://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
>
>


-- 
-----------------------------------------------------------------------------------------

Nesrine ZOUARI
Computer Engineering Student
Department of Computer Engineering and Applied Mathematics
National Engineering School of Sfax (ENIS)
University of Sfax-Tunisia
Tel: +216 52 620 475

[-- Attachment #1.2: Type: text/html, Size: 40382 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Re: Babeltrace Patch

[Jonathan Rajotte-Julien]

Hi Nesrine,

> I have already tried Tracecompass and lttng-scope and they match exactly my
> project use case.
> 
> But as I said in the beginning, I am working on my *graduation project* and
> I have to develop *client/server applications communicating through TCP
> socket (in C language).*

Unless you expose an actual problem that is not taken care of by one
of the existing tools and that you are willing to actually work on solving it,
I do not think this mailing list is appropriate for what you are trying to achieve.

> 
> This is a short description of my project requirements:
> My project is divided into two parts:
> 
> *      1)* Collecting traces from Qemu (It is already an instrumented user
> space application).
> 
> *       2)* Sending the collected traces to a third-party tool for analysis.
> 
> * Qemu, LTTng demons and my server application are running on the same
> Linux machine.

I guess this take care of 1.

> 
> * The client application is running on a remote WINDOWS machine.

Sure why not, we do not have anything against Windows.

There is already efforts to port Babeltrace 1.5/2 to Windows using
Cygwin.[1] [2]

[1] https://ci.lttng.org/view/Babeltrace/job/babeltrace_stable-1.5_winbuild/
[2] https://ci.lttng.org/view/Babeltrace/job/babeltrace_stable-2.0_winbuild/

>    Client is able now to control the trace remotely (start and stop) and
> get the trace collected in a text file.
> 
> 
> *This is what I am trying to do right now:*
> 
> Instead of writing the traces to a text file, I would like to send those
> traces over TCP to my client application.
> So I think that the problem now is* how to make Babeltrace convert CTF
> traces and send them to my client application through TCP.*

If you absolutely do not want to use the available tools and do not want
to use ctf and/or live protocol as the intermediate format for transfer then you
could simply pipe the output from babeltrace to netcat (or your "application/server") and have a
process on the other side (Windows) listening on a port and do whatever you like. This will
come with all the pitfalls of piping text over the network.

I do think that the live protocol need some love and could profit from another
client implementation (apart from babeltrace). As for the actual ctf conversion
there is some java ctf reader [3] [4] that "should work out of the box" on
Windows. A java live ctf reader library/utility could be a nice project actually.

Based on the artifact found here [5], you can run babeltrace on Windows and pipe it
to your application directly.

Based on the artifact found here [6], lttng-relayd works on Windows.

So you got, lttng-relayd and babeltrace available on Windows giving you a lot of
possibilities on how to transfer your data to your analysis pipeline. But as you
said, this does not fit your "graduation project".

[3] https://github.com/efficios/ctf-java/tree/master/ctfreader
[4] http://git.eclipse.org/c/tracecompass/org.eclipse.tracecompass.git/tree/ctf
[5] https://ci.lttng.org/view/Babeltrace/job/babeltrace_stable-1.5_winbuild/19/arch=cygwin,build=std,conf=std/artifact/build/bin/
[6] https://ci.lttng.org/view/LTTng-tools/job/lttng-tools_stable-2.10_winbuild/arch=cygwin,babeltrace_version=stable-1.5,build=std,conf=relayd-only,liburcu_version=stable-0.9/50/artifact/build/bin/

> 
> I would be grateful if you will give me some hints or another idea to
> satisfy my project requirements.

Since that you are more interested in the limited scope of your project I doubt
that we have any incentive to provide you ideas. This is not the point of this
mailing list. This mailing list is about improving the LTTng ecosystem.

Cheers

-- 
Jonathan Rajotte-Julien
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

Babeltrace Patch

[Nesrine Zouari]

[-- Attachment #1.1: Type: text/plain, Size: 1110 bytes --]

Hello,

I am computer engineering student and I am actually working on my
graduation project which is about Qemu Trace.

In this project, Qemu is considered as a user-space instrumented
application.

I have used:

1) LTTng-Tools to control Qemu trace.

2) Babeltrace to convert the CTF traces to a human readable text.

Now, I aim to develop a patch to the Babeltrace. Instead of printing the
traces on the console or in a file, I would like to send the traces over
TCP/IP to a third-party tool for processing.
My third-party tool is installed on a windows machine. For this reason, the
use of LTTng relay daemon will not be a good solution.

My question is the following:

To which file (of the Babeltrace source code) should I make changes to
answer my use case?

Best regards,

-----------------------------------------------------------------------------------------

Nesrine ZOUARI
Computer Engineering Student
Department of Computer Engineering and Applied Mathematics
National Engineering School of Sfax (ENIS)
University of Sfax-Tunisia
Tel: +216 52 620 475


‌

[-- Attachment #1.2: Type: text/html, Size: 14797 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev