rfac: Observablity blog to include new long conn metrics and accesslogs #176
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kmesh-net ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
yp969803
changed the title
|
@yp969803 hello , please add the author as you into the similar kind of |
Signed-off-by: Yash Patel <[email protected]>
yp969803
force-pushed
the
issue1325kmeshObsBlog
branch
from
ca945e9 to
280b387
Compare
|
@LiZhenCheng9527 can u review and merge |
|
/retest |
|
@yp969803 You should rebase on the main branch, https://github.com/kmesh-net/website/pull/172/files fixed a timeout issue |
|
Adding label Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
@hzxuzhonghu done |
There was a problem hiding this comment.
Cool, have you supplemented document https://deploy-preview-176--kmesh-net.netlify.app/docs/transpot-layer/l4-metrics?
LGTM
| }; | ||
| ``` | ||
|
|
||
| In addition to this data that can be accessed directly, Kmesh temporary data while the link is being established. Obtain data such as link duration from the previously temporarily recorded data when the link is closed. | ||
| In addition to the TCP data that can be accessed directly, Kmesh temporarily records supplementary information during the connection establishment phase, such as the start time, connection direction, and the last report time. The last report time is used to periodically report connection metrics. After each report, Kmesh updates the last report time to the current timestamp, while also utilizing other stored information to enrich the reported data. |
There was a problem hiding this comment.
connection direction or traffic direction @LiZhenCheng9527
blog/kmesh-observability/index.md
Outdated
|
|
||
| ## How to Handle Data | ||
| Connection data is published to a ring buffer, allowing userspace applications to access it. Data is reported at key stages of the connection lifecycle: during connection establishment, at regular intervals throughout the connection's duration, and upon connection closure. |
There was a problem hiding this comment.
| Connection data is published to a ring buffer, allowing userspace applications to access it. Data is reported at key stages of the connection lifecycle: during connection establishment, at regular intervals throughout the connection's duration, and upon connection closure. | |
| Connection stats is written to a ring buffer, allowing userspace applications to access it. Data is reported at key stages of the connection lifecycle: during connection establishment, at regular intervals throughout the connection's duration, and upon connection closure. |
blog/kmesh-observability/index.md
Outdated
|
|
||
| After Kmesh is done with the data from this link, it will pass the data to the user state through ringbuf. | ||
| ## How to Handle Data |
There was a problem hiding this comment.
Maybe more specific
| ## How to Handle Data | |
| ## How to Handle TCP Stats |
blog/kmesh-observability/index.md
Outdated
|
|
||
| After parses the data from ringbuf in the use space, Kmesh builds `metricLabels` based on the linked source and destination information. it then updates the cache in the `metricController`. | ||
| After parsing the data from ringbuf in the use space, Kmesh builds `metricLabels` based on the linked source and destination information. it then updates the cache in the `metricController`. |
There was a problem hiding this comment.
| After parsing the data from ringbuf in the use space, Kmesh builds `metricLabels` based on the linked source and destination information. it then updates the cache in the `metricController`. | |
| After parsing the data from ringbuf in the user space, Kmesh builds `metricLabels` based on the linked source and destination information. It then updates the cache in the `metricController`. |
blog/kmesh-observability/index.md
Outdated
|
|
||
| The architecture diagram is shown below: | ||
|
|
||
|  | ||
|  |
There was a problem hiding this comment.
The image is not seen after zoom in
There was a problem hiding this comment.
You can draw with https://app.diagrams.net/
| | kmesh_tcp_workload_conntections_failed_total | The total number of TCP connections failed to a workload | | ||
| | Name | Description | | ||
| | ---------------------------------------------- | ---------------------------------------------------------------------------------------------- | | ||
| | `kmesh_tcp_workload_connections_opened_total` | The total number of TCP connections opened to a workload | |
There was a problem hiding this comment.
BTW, i think the description is bad, not your fault though
Signed-off-by: Yash Patel <[email protected]> rfac: changed image type to svg in obs blog Signed-off-by: Yash Patel <[email protected]>
yp969803
force-pushed
the
issue1325kmeshObsBlog
branch
from
3bd1219 to
5dd4c82
Compare
|
@hzxuzhonghu done the changes |
Fixes kmesh-net/kmesh#1325