We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems that we need to recheck our logic as there are no stats metrics yflow.ypoint* Expected metrics (openkilda-metrics.md):
<prefix>.yflow.ypoint.bits
<prefix>.yflow.ypoint.bytes
<prefix>.yflow.ypoint.packets
Tags:
y_flow_id
unknown
flowid
direction
forward
reverse
undefined
is_y_flow_subflow
true
Note, the meter.yflow.ypoint* metrics are present.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
It seems that we need to recheck our logic as there are no stats metrics yflow.ypoint*
Expected metrics (openkilda-metrics.md):
Y-flow Y point rule metrics
<prefix>.yflow.ypoint.bits
- total size of all packets which were processed by the Y-flow's rule in the Y point in bits<prefix>.yflow.ypoint.bytes
- total size of all packets which were processed by the Y-flow's rule in the Y point in bytes<prefix>.yflow.ypoint.packets
- total count of packets which were processed by the Y-flow's rule in the Y pointTags:
y_flow_id
- String: ID of a Y-flow which a rule belongs to,unknown
if there is no information about a Y-flowflowid
- String: ID of a sub flow which a rule belongs to,unknown
if there is no information about a flowdirection
- String: direction of flow traffic:forward
,reverse
orundefined
is_y_flow_subflow
Boolean:true
as a sub flow belongs to a Y-flowNote, the meter.yflow.ypoint* metrics are present.
The text was updated successfully, but these errors were encountered: