部署与运维

dt-obs-network-flows

dynatrace/dynat…e-for-ai

Network flow analysis in Dynatrace across three sources: OneAgent flows (host/process/pod-to-peer connections in the `default_network_flows` Grail bucket), NetFlow/IPFIX/sFlow (via an OpenTelemetry Collector), and cloud flow logs (AWS VPC / Transit Gateway; Azure and GCP planned). Use to analyze traffic between entities, find top talkers by bandwidth, map communication dependencies, investigate connection health (resets, timeouts, retransmissions, RTT), and resolve peers to monitored entities. Routes each question to the right source; source-specific DQL lives in the reference files. Trigger: "network flows", "top talkers", "traffic between hosts", "connection resets", "TCP retransmissions", "RTT", "pod connections", "network dependencies", "NetFlow", "IPFIX", "sFlow", "VPC flow logs", "cloud network traffic". Do NOT use for host NIC throughput or packet drops (use dt-obs-hosts), service request rate or latency (use dt-obs-services), or synthetic/uptime monitoring (use dt-obs-ext-monitors).

  • 969 次安装
  • 170 星标
  • 收录于

安装命令

npx skills add https://github.com/dynatrace/dynatrace-for-ai --skill dt-obs-network-flows

SKILL.md

Network Flows Skill

Analyze network traffic in Dynatrace across three flow data sources. This skill covers the use cases network flows enable and routes each question to the right source and reference file. The detailed, source-specific DQL lives in the reference files.

What Network Flows Tell You

Network flow data answers questions that metrics and traces cannot:

  • Who talks to whom — communication dependencies between hosts, processes, pods, services, and external endpoints
  • Top talkers — which entities generate the most traffic, by bytes or connection count
  • Connection health — resets, timeouts, retransmissions, and round-trip time (RTT) per conversation
  • Traffic composition — protocol (TCP/UDP), destination ports, direction (client vs server)
  • Peer resolution — mapping raw IP:port peers back to monitored entities (host, process, pod, service) or flagging them as external

The Three Flow Sources

Choose the source based on where the traffic is and what is capturing it. When more than one applies, prefer the source with the richest entity context (usually OneAgent).