f5_network_interface_bits_in_total value issue
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- prometheus
- Domain
- observability-sre
Research direction
Reproduce the discrepancy in the F5 internal UDF AST lab using f5_node_bytes_in_total, f5_pool_bytes_in_total, and f5_network_interface_bits_in_total. Compare the results with the Prometheus and demo dashboards; done means explaining the conversion mismatch and identifying the correction needed for interface totals to align with pool or node data.
Written by the indexing model from the issue text.
Description
Issue:
f5_network_interface_bits_in_total does not seem to be correct when compared to the other metrics for pool and node.
AST version is v0.9.6.
Customer issue:
The customer is pulling the Cisco metrics for the ports and wants to match the data volume to the big-ip interface. This does not work, the values are drastically different but it does match using the pool or node.
Explanation:
On a simple big-ip config pulling in the total pool, node and external interface data the total bits/bytes are not adding up to the same value after the recommended "/8", the graphing trends look to be very similar patterns but the interface is a lot bigger in values.
Expectation was they should match interface in total data to the pools in as all traffic is coming in.
Metrics being used are:
- f5_node_bytes_in_total
- f5_pool_bytes_in_total
- f5_network_interface_bits_in_total
The interface data if divided by 4 matches, not sure why it should be divides by 8 to move from bits to bytes per the prometheus and demo dashboards.
Reproducing:
This was reproducible on the F5 internal UDF AST lab regarding the interface data.
Divide by 4 on interface - similar graphs:
Divide by 8 on interface - interface drops, not possible it should match the pool/node in:
- Dominant language
- Python
- Stars
- 106
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from f5devcentral/application-study-tool
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 62/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 3/5 1-2 days Newbie friendliness 50/100
f5devcentral/application-study-tool#267 · 7 comments ·
All issues in f5devcentral/application-study-tool
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100