Skip to content
Start free

Kubeadapt MCP

Ask about network cost

Ask an AI tool connected to Kubeadapt MCP what Kubernetes network traffic costs: internet egress, cross-zone traffic, and who a workload talks to.

Last updated

Ask your AI tool what network traffic costs and it answers with traffic and its cost by billing class, such as internet egress and cross-zone, plus the workloads that send the most and the destinations they send to. For one workload, it shows who that workload talks to, across which zones, and what that traffic costs per month.

This example needs a connection with the Network costs data kind, in an organization that uses Network Intelligence. The pricing question needs Costs and carbon.

Ask

plaintext
What did network traffic cost us last month, by billing class?
plaintext
What does cross-zone traffic cost us, and which workload pairs cause most of it?
plaintext
Which internet destinations do we send the most data to, and what does that cost?
plaintext
Who does the checkout service talk to, in which direction, and what does that traffic cost per month?
plaintext
Which clusters send no network data?
plaintext
Which network rates is the prod cluster priced with, and which traffic classes are billed?

What happens

ToolWhat it returns here
query_network_costsBytes sent, internet egress, cross-zone and unresolved traffic, cost by billing class, the top external destinations and sending workloads, pending network recommendations, and with include_zones the zone-to-zone matrix and the workload pairs that cross zones most.
get_workload_trafficFor one workload: bytes sent and received with the change on the previous period, its monthly network cost, the protocol mix, and its top peers with direction, zones crossed, protocol, volume, connections, billing class and monthly cost.
get_pricingThe cluster's network rate for each traffic class, whether each is billed, and where each rate comes from.
searchThe workload's id from its name, such as "checkout".

What the answer contains

  • Volumes and dollars. bytes_sent, internet_egress_bytes, cross_zone_bytes and unresolved_bytes, each with its cost, and cost_by_class with billed bytes per class and whether it is priced.
  • Top lists. top_destinations and top_senders, ranked by cost, or by bytes when nothing is priced; top_ranked_by says which.
  • Savings. Pending network recommendations with their monthly saving, confidence and effect on high availability.
  • Coverage. clusters_without_network_data lists clusters in scope that sent no network data. Their traffic is unknown, not zero, and the answer says so.
  • Provenance. The window in UTC calendar days and the measured window. Network figures are marked as estimated: they apply list rates to measured bytes.

Missing is not zero. A null cost means the traffic has no price, never that it cost nothing. When some clusters have no network pricing, their traffic still counts in bytes and the dollar totals are a floor.

Follow-ups

plaintext
For the workload that sends the most to the internet, which destinations does it reach?
plaintext
Show only cross-zone pairs inside the prod cluster for the last 7 days.
plaintext
What is checkout's total cost, network included, over the same window?
plaintext
Open Network Intelligence in Kubeadapt.

Limits

  • Measured clusters only. Traffic is measured on clusters where Kubeadapt's network monitoring is installed and reporting. See eBPF Agent.
  • Estimates, not your invoice. Dollar figures apply rates to measured bytes. They can differ from your cloud provider's bill.
  • Received traffic undercounts. Inbound figures are derived and not measured everywhere, so treat them as a minimum.
  • Windows. query_network_costs reads the last 30 complete days by default and get_workload_traffic the last 7; either takes up to 731 days. Days older than Kubeadapt keeps network detail for, or from before collection started, are reported as not covered.
  • No pricing, no dollars. If no cluster in scope has network pricing, the answer gives traffic volumes only. An admin can set the rates in the cluster's network pricing settings.
  • Read-only. Kubeadapt MCP can't change pricing, routing or workloads.

Related