-
Sub-task
-
Resolution: Done
-
Major
-
None
-
None
-
None
Currently the client side return the tracing info in plaintext format encapsulated in self-defined format:
EventCategory [duration / sinceRequestTime | duration/requestTime % ]
Here is the client side tracing info sample extracted from response headers:
HTTP/1.1 200 OK X-RESTEasy-Tracing-026: MBW [ ---- / 23.64 ms | ---- %] [org.jboss.resteasy.plugins.providers.DataSourceProvider @39c3d668] is skipped X-RESTEasy-Tracing-027: MBW [ ---- / 23.83 ms | ---- %] [org.jboss.resteasy.plugins.providers.FileRangeWriter @5008fa2c] is skipped X-RESTEasy-Tracing-028: MBW [ ---- / 23.97 ms | ---- %] [org.jboss.resteasy.plugins.providers.InputStreamProvider @6f7a2863] is skipped X-RESTEasy-Tracing-029: MBW [ ---- / 24.42 ms | ---- %] WriteTo by org.jboss.resteasy.plugins.providers.StringTextStar X-RESTEasy-Tracing-030: WI [ 3.72 / 26.35 ms | 13.81 %] [org.jboss.resteasy.plugins.interceptors.GZIPEncodingInterceptor @6ef888f6 #4000] AFTER context.proceed() X-RESTEasy-Tracing-031: WI [ 4.37 / 26.64 ms | 16.23 %] WriteTo summary: 1 interceptors X-RESTEasy-Tracing-032: RESP-FILTER [ 5.95 / 26.77 ms | 22.09 %] Response summary: 1 filters X-RESTEasy-Tracing-033: FINISHED [ ---- / 26.95 ms | ---- %] Response status: 200 ...
We should provide option to the users to get JSON formatted tracing info, so it can be better consumed by other streaming apps. A sample usage scenario:
- The JSON data can be processed with Kafka with it's REST proxy, and further processed by KSQL.