Updated Home (markdown)

master
Richard van der Hoff vor 2 Jahren
Ursprung
Commit
57aa7a1c0c
1 geänderte Dateien mit 1 neuen und 24 gelöschten Zeilen
  1. +1
    -24
      Home.md

+ 1
- 24
Home.md

@@ -76,31 +76,8 @@ If you want to paste that output into a github issue or matrix room, please reme

What do all those fields in the 'Processed' line mean?
---
See https://matrix-org.github.io/synapse/develop/usage/administration/request_log.html.

The log format can vary slightly depending on your log configuration, but here is a breakdown of the example above:

* `2019-02-14 22:35:08,196`: date/time when we finished processing the request
* `synapse.access.http.8008`: logger name. For 'Processed' lines, the logger name is `synapse.access.http.` plus the TCP port that the request came in on
* `302`: the line number where the request was logged. Useless for 'Processed' lines.
* `INFO`: the log level. Always `INFO` for 'Processed' lines.
* `GET-37`: the request tag
* `::1`: the client IP address
* `8008`: the TCP port where the request came in (again)
* `{@richvdh:localhost}`: if the request came from an authenticated user or server, their user id or server_name.
* `Processed request:`
* `0.173sec/0.001sec`:
* time between the request arriving and synapse finishing its processing of it (the "processing time").
* time between synapse finishing its processing of the request and the response being sent to the client: ie, the time taken to stream the response to the client. Note that this may be negative if the client dropped the connection before synapse finished processing the request.
* `(0.002sec, 0.000sec)`: user- and system- cpu time spent processing this request.
* `(0.027sec/0.026sec/2)`:
* time spent waiting for a connection to the database during this request (the "database scheduling time"). (Note that this may be higher than the request processing time, since synapse may make several database requests in parallel, each of which contributes to this scheduling time.)
* time spent running database transactions, excluding scheduling time (the "database transaction time"). (Again, may be higher than the request processing time).
* the number of database transactions performed.
* `687B`: the length of the response body (687 bytes, in this case).
* `200`: the HTTP response code. Followed by an exclamation mark (`!`) if the client dropped the connection before we sent the response.
* `"GET /_matrix/client/r0/sync HTTP/1.1"`: the http request line, including the path of the requested url.
* `"Mozilla/5.0 ..."`: the user-agent of the client.
* `[0 dbevts]`: the number of Matrix events which were fetched from the database to fulfil this request.

What are the biggest rooms on my server?
---


Laden…
Abbrechen
Speichern