wu-sheng opened a new pull request, #100:
URL: https://github.com/apache/skywalking-query-protocol/pull/100
```
# Since 9.3.0
# Record is a general and abstract type for collected raw data.
# In the observability, traces and logs have specific and well-defined
meanings, and the general records represent other
# collected records. Such as sampled slow SQL statement, HTTP request raw
data(request/response header/body)
extend type Query {
# Query collected records with given metric name and parent entity
conditions, and return in the requested order.
readRecords(condition: RecordCondition!, duration: Duration!): [Record!]!
}
```
A new query protocol is being added, to replace the `readSampledRecords`.
This would be a compatible upgrade to support more use cases for sampled
records(such as in instance level) and incoming HTTP header/body
collecting(through ebpf agent).
In ebpf case, we would be able to sample HTTP request/response according to
latency threshold, even 100% sampling. And link those records with trace
ID/span ID decoded from the sw8(skywalking)/b3(zipkin) header. Then we could
have this diagnose workflow, `slow HTTP request` -> `TRACE view` -> `RPC span
with attached event`. The event includes the HTTP request/response in step <1>,
as well as statistics of network events(ref
https://github.com/apache/skywalking-data-collect-protocol/pull/77)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
