Re: [tracecompass-dev] Questions about trace-server TSP API

[tracecompass developer discussions <tracecompass-dev@xxxxxxxxxxx>]

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> 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
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/tracecompass-dev