You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some discussions with @StevenLeRoux, @BlackYoup and @Wonshtrum.
We found out that Sōzu need to provides a little more information about request and response.
So, I use this issue to make a summary of what we need.
Firstly, I will remember that we have to tackle the issue #641, #892 and #804.
What we already have
Access logs
Currently, when we handle request (TCP, HTTP[s] or WS[s]) will write following access logs.
response time : the total duration of the request service time : the total duration that Sozu took to treat the request websocket context: the value is - if the protocol is TCP
You can find the code source that output those logs here:
Today, we have a bunch of metrics and we do not use all of them.
We should investigate.
To do so, we have to:
make a proper list of metrics (classname+labels+kind+description).
Then, establish the cardinality of each one and segregate them in two parts:
The one that are Sōzu-related (event loop, worker, etc..)
The one that are cluster-related (status code, response time, service time, cluster response time, data transfer, etc..)
The cluster-related have to be labeled with the cluster identifier and optionaly the backend identifier.
What is missing
Access logs
To us, it miss some informations in access logs as :
client rtt: the time in millisecond to establish a connection between the client and Sōzu
server rtt: the time in millisecond to establish a connection between Sōzu and the backend
cluster response time: the time in millisecond between the end of the transfer of the request body and the response header betweend Sōzu and the backend
data transfer time: the total duration in millisecond of transfering data between the client to the backend and vice-versa
Hello there 👋,
After some discussions with @StevenLeRoux, @BlackYoup and @Wonshtrum.
We found out that Sōzu need to provides a little more information about request and response.
So, I use this issue to make a summary of what we need.
Firstly, I will remember that we have to tackle the issue #641, #892 and #804.
What we already have
Access logs
Currently, when we handle request (TCP, HTTP[s] or WS[s]) will write following access logs.
Below, an explanation of the above access logs:
01H0FXX3VTR8T3B1K0ZHXQZZNQ
MyCluster
the-backend-to-my-app
127.0.0.1:50444 -> 127.0.0.1:1026
61ms
4959μs
79
68535
key=value
HTTPS-TLS1.3
lolcatho.st:8443
200
GET
/
01H0FXZVQK7RK3W55X7V26M259
TcpTest
TcpTest-0-127.0.0.1:4000
127.0.0.1:52378 -> 127.0.0.1:4000
19ms
168μs
79
68522
owner=John, uuid=3f740af1-45fd-45ce-b61f-17bf1a51505f
TCP
-
You can find the code source that output those logs here:
TCP or WS
sozu/lib/src/protocol/pipe.rs
Lines 275 to 287 in 3aea15c
sozu/lib/src/protocol/pipe.rs
Lines 328 to 340 in 3aea15c
HTTP
sozu/lib/src/protocol/http/mod.rs
Lines 614 to 628 in 3aea15c
sozu/lib/src/protocol/http/mod.rs
Lines 682 to 696 in 3aea15c
sozu/lib/src/protocol/http/mod.rs
Lines 758 to 773 in 3aea15c
Metrics
Today, we have a bunch of metrics and we do not use all of them.
We should investigate.
To do so, we have to:
What is missing
Access logs
To us, it miss some informations in access logs as :
Metrics
We should investigate first the item above.
Registry:
The text was updated successfully, but these errors were encountered: