-**qps**: 在html下从右到左分别是过去60秒,60分钟,24小时,30天的平均qps(Queries Per Second)。纯文本下是10秒内([-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)控制)的平均qps。
[/status](http://brpc.baidu.com:8765/status) shows primary statistics of services. They shares the same sources with [/vars](../cn/vars.md) , except that they are grouped by services.
[中文版](../cn/status.md)
[/status](http://brpc.baidu.com:8765/status) shows primary statistics of services inside the server. The data sources are same with [/vars](vars.md), but stats are grouped differently.
![img](../images/status.png)
![img](../images/status.png)
Meaning of the fields above:
Meanings of the fields above:
-**non_service_error**: the count of errors except the ones raised by the services. For example, it is a *non_service_error* that the client closes connection when the service is processing requests since no response could be written back, while it counts in the *service error* when the connection established internally in the service is broken and the service fails to get reponse from the remote side.
-**non_service_error**: number of errors raised outside processing code of the service. For example, the error that server can't write response back due to a broken connection which had been closed by the client, is a *non_service_error* because the service processing already ends. As a contrast, failing to access back-end servers during the processing is an error of the service, not a *non_service_error*. Even if the response written out successfully stands for failure, the error is counted into the service rather than *non_service_error*.
-**connection_count**: The number of connections to the server, excluded the ones connected to remote.
-**connection_count**: number of connections to the server from clients, not including number of outward connections which are displayed at /vars/rpc_channel_connection_count.
-**example.EchoService**: Full name of the service, including the package name。
-**example.EchoService**: Full name of the service, including the package name defined in proto.
-**Echo (EchoRequest) returns (EchoResponse)**: Signature of the method, a services can have multiple methods, click request/response and you can check out the corresponding protobuf message.
-**Echo (EchoRequest) returns (EchoResponse)**: Signature of the method. A service can have multiple methods. Click links on request/response to see schemes of the protobuf messages.
-**count**: Number of requests that are succesfully processed.
-**count**: Number of requests that are succesfully processed.
-**error**: Number of requests that meet failure.
-**error**: Number of requests that are failed to process.
-**latency**: On the web page it shows average latency in the recent *60s/60m/24h/30d* from *right to left*. On plain text page it is the average latency in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval).
-**latency**: average latency in recent *60s/60m/24h/30d* from *right to left* on html, average latency in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)) on plain texts.
-**latency_percentiles**: The percentail of latency at 50%, 90%, 99%, 99.9% in 10 seconds(specified by[-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)),it shows adtional historical values on the web page.
-**latency_percentiles**: 50%, 90%, 99%, 99.9% percentiles of latency in 10 seconds(specified by[-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)). Curves with historical values are shown on html.
-**latency_cdf**: Anther view of percentiles like histogram,only available on web page.
-**latency_cdf**: shows percentiles as [CDF](https://en.wikipedia.org/wiki/Cumulative_distribution_function), only available on html.
-**max_latency**: On the web page it shows the max latency in the recent *60s/60m/24h/30d* from *right to left*. On plain text page it is the max latency in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval).
-**max_latency**: max latency in recent *60s/60m/24h/30d* from *right to left* on html, max latency in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)) on plain texts.
-**qps**: On the web page it shows the qps in the recent *60s/60m/24h/30d* from *right to left*. On plain text page it is the qps in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval).
-**qps**: QPS(Queries Per Second) in recent *60s/60m/24h/30d* from *right to left* on html. QPS in recent 10s(by default, specified by [-bvar_dump_interval](http://brpc.baidu.com:8765/flags/bvar_dump_interval)) on plain texts.
-**processing**: The number of requests that is being processed by the service. If this is
-**processing**: Number of requests being processed by the service. If this counter can't hit zero when the traffic to the service becomes zero, the server probably has bugs, such as forgetting to call done->Run() or stuck on some processing steps.
You can extends your servcies with [brpc::Describable](https://github.com/brpc/brpc/blob/master/src/brpc/describable.h) to customize /status page.
Users may customize descriptions on /status by letting the service implement [brpc::Describable](https://github.com/brpc/brpc/blob/master/src/brpc/describable.h).