-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
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
[Infrastructure UI] Add network traffic to Hosts table #142137
Conversation
Pinging @elastic/infra-monitoring-ui (Team:Infra Monitoring UI) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The formula looks good and I was able to correlate the values to the inventory. It's neat to see it translated to lens like this 👏
@elasticmachine merge upstream |
@elasticmachine merge upstream |
💛 Build succeeded, but was flaky
Failed CI StepsTest FailuresMetrics [docs]Async chunks
History
To update your PR or re-run it, just comment with: |
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Closes #139316
Adds Inbound (rx) and outbound (tx) network traffic to the table using the same fields and formulas where we calculate network traffic in Infra. So when viewing the Inventory tx/rx traffic it should be in the same ballpark as these. The formula used is: (average(host.network.ingress.bytes) * 8) / (max(metricset.period) / 1000) and (average(host.network.egress.bytes) * 8) / (max(metricset.period) / 1000). Similar to inventory rx and tx. One addition is multiplying by 8 because Lens formatter assumes bits whereas we add this logic in the formatter. For more information on the formula see #134471
This is easiest reviewed by checking it out. You would need to enable the technical preview in Advanced Settings for the Hosts view. You can also log getLensHostsTable(dataView, query) and paste that into the Lens "Debug in Playground" and save it to view directly in Lens. This requires starting kibana with
yarn start --run-examples