-**Probe Protocol**. Include the descriptions and defines about how agent send collected metric data and traces, also the formats of each entities.
-**Probe Protocol**. Include the descriptions and definitions about how agent send collected metric data and traces, also the formats of each entities.
-**Query Protocol**. The backend provide query capability to SkyWalking own UI and others. These queries are based on GraphQL.
## Probe Protocol
## Probe Protocols
They also related to the probe group, for understand that, look [Concepts and Designs](../concepts-and-designs/README.md) document.
These groups are **Language based native agent protocol**, **Service Mesh protocol** and **3rd-party instrument protocol**.
## Language based native agent protocol
### Language based native agent protocol
This protocol is combined from two parts:
*[Cross Process Propagation Headers Protocol](Skywalking-Cross-Process-Propagation-Headers-Protocol-v1.md) is for in-wire propagation.
which is usually used to carrier the necessary info to build trace.
*[SkyWalking Trace Data Protocol](Trace-Data-Protocol.md) define the communication way and format between agent and backend.
## Service Mesh probe protocol
\ No newline at end of file
### Service Mesh probe protocol
The probe in sidecar or proxy could use this protocol to send data to backendEnd. This service provided by gRPC, requires
the following key info:
1. Service Name or ID at both sides.
1. Service Instance Name or ID at both sides.
1. Endpoint. URI in HTTP, service method full signature in gRPC.
1. Latency. In milliseconds.
1. Response code in HTTP
1. Status. Success or fail.
1. Protocol. HTTP, gRPC
1. DetectPoint. In Service Mesh sidecar, `client` or `server`. In normal L7 proxy, value is `proxy`.