[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tracecompass-dev] Questions about trace-server TSP API
|
Hi Qing
Not much, right now the documentation is still weak. The main documentation is the TSP description itself which you can find at [1].
By the way, a Python client has been started to query a trace server using the TSP. It's in infancy state and has only a subset of the features. However, it helps me to understand and quickly try things using a Python script. See [2] for the Python client.
BR
Bernd
[1] https://theia-ide.github.io/trace-server-protocol/
[2] https://github.com/theia-ide/tsp-python-client/
________________________________________
From: tracecompass-dev-bounces@xxxxxxxxxxx <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Sent: April 23, 2020 11:59 AM
To: tracecompass developer discussions
Subject: Re: [tracecompass-dev] Questions about trace-server TSP API
Hi Patrick,
Is there any user guide for TSP API? Because I want to investigate how it works of all, like how to get the raw data, analysis and so on.
Best Regards,
-qing
From: <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Reply-To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Date: Thursday, April 23, 2020 at 11:36 PM
To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Subject: Re: [tracecompass-dev] Questions about trace-server TSP API
Hi Patrick,
Thank you for your help. The trace can be opened after giving a correct location.
-qing
From: <tracecompass-dev-bounces@xxxxxxxxxxx> on behalf of tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Reply-To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Date: Thursday, April 23, 2020 at 11:21 PM
To: tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>
Subject: Re: [tracecompass-dev] Questions about trace-server TSP API
Hi Qing,
In your typeId value string there are spaces before and after. They should not be there.
But as far as I can tell this should not have mattered, it should select the most valid trace type automatically, the typeId is just a hint.
A valid Linux Kernel Trace is also a Generic CTF Trace.
I wonder if the problem is not that your TSP server is not finding a valid CTF trace at the given location. Is this location a folder that contains a "metadata" file?
Patrick
On Thu, Apr 23, 2020 at 10:47 AM tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx<mailto:tracecompass-dev@xxxxxxxxxxx>> wrote:
Hi Guys,
Today I have tried to use TSP API of trace-server. But I got some problems on it.
API:
curl -X POST http://localhost:8080/tsp/api/traces -H 'accept: application/json' -H 'cache-control: no-cache' -H 'Content-Type: application/json' -d '{"parameters": {"name":"trace1", "uri":"/home/chiq/kernel-trace", "typeID": " org.eclipse.linuxtools.tmf.core.type.ctf "}}'
Error code:
406
Error message:
No trace types found to match location /home/chiq/kernel-trace
There are two types of these traces: 1, Linux Kernel Trace
2, Generic CTF Trace
What typeID are these traces of TSP API?
Thanks for your help.
-qing
_______________________________________________
tracecompass-dev mailing list
tracecompass-dev@xxxxxxxxxxx<mailto:tracecompass-dev@xxxxxxxxxxx>
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tracecompass-dev<https://protect2.fireeye.com/v1/url?k=cdcc484c-9145925c-cdcc08d7-0cc47ad93e2a-fe48ffc4b92892e9&q=1&e=b71a613f-c0f4-4ea8-ad69-abdbf3de4403&u=https%3A%2F%2Fnam04.safelinks.protection.outlook.com%2F%3Furl%3Dhttps%253A%252F%252Fwww.eclipse.org%252Fmailman%252Flistinfo%252Ftracecompass-dev%26data%3D02%257C01%257Cchiq%2540vmware.com%257C7d65b3feebfd4fa9648e08d7e79c0f2f%257Cb39138ca3cee4b4aa4d6cd83d9dd62f0%257C0%257C0%257C637232529789819862%26sdata%3DRO0iMBwmrrGqMs%252BYfjpNxflIXMAxuycRlEtAsPXorGY%253D%26reserved%3D0>
