Dt Obs Network Flows

Organization

Dynatrace

dt-obs-network-flows

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).

Overview

Publisher	Dynatrace
Repository	`dynatrace-for-ai`
Skill name	`dt-obs-network-flows`
Stars	156
Forks	30
Bundled files	7
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
7 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Dynatrace on GitHub. Read the source before you install it.

Installation

Install the Dt Obs Network Flows AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Dynatrace/dynatrace-for-ai.git /tmp/dynatrace-for-ai
mkdir -p .claude/skills
cp -r /tmp/dynatrace-for-ai/skills/dt-obs-network-flows .claude/skills/dt-obs-network-flows

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Dt Obs Network Flows in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Dt Obs Network Flows on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Dt Obs Network Flows is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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).

Source	Captured by	Data location	Entity context	Use when
OneAgent flows	OneAgent network agent on the host	events in the `default_network_flows` Grail bucket	Rich — the capturing entity (client or server) resolved to host / process / pod smartscape IDs; the remote peer as IP:port	Traffic to/from OneAgent-monitored hosts, processes, or Kubernetes pods. The default and most detailed source.
NetFlow / IPFIX / sFlow	Network devices (switches, routers), ingested via an OpenTelemetry Collector	logs (`otel.scope.name == "otelcol/netflowreceiver"`; recommend routing to a dedicated bucket)	Device/interface level — raw IPs, exporter, interfaces; no smartscape entities	Traffic seen by network hardware. Covers east-west and north-south flows at the network layer.
Cloud flow logs	Cloud provider (AWS VPC / TGW; Azure, GCP not yet documented)	logs (`log.type == "aws.vpc"` / `"aws.tgw"`; recommend routing to a dedicated bucket)	Cloud resource level — VPC / subnet / AZ / ENI, TGW attachment; raw IPs, no smartscape entities	Traffic within/across cloud networks, including managed services and resources without an agent.

Routing logic

Is the traffic to/from a OneAgent-monitored host, process, or pod? → OneAgent flows. See references/oneagent-flows/oneagent-flows.md.
Is it device-level or from unmonitored hosts? → NetFlow. See references/netflow/netflow.md.
Is it cloud-network / managed-service traffic? → Cloud flow logs (per provider). AWS: references/cloud-flows/aws/aws.md.

The three sources overlap. A pod-to-pod flow may appear in both OneAgent flows (with full pod context) and cloud flow logs (as ENI-to-ENI). Lead with the source that carries the entity context the user needs, and mention the alternative only if the primary source has no data.

Related Network Data in Dynatrace

Network flows are one part of Dynatrace's network observability. Route to these when the question is not about flows:

The user wants…	Use
Host NIC throughput, link utilization, packet drops/errors	dt-obs-hosts → `references/host-metrics.md` (Network Monitoring section)
Process-level network I/O and TCP connection quality metrics	dt-obs-hosts → `references/process-monitoring.md`
Kubernetes pod connections and cluster network topology	dt-obs-kubernetes
Service request rate, latency, error rate	dt-obs-services
External / synthetic uptime and network-availability monitors	dt-obs-ext-monitors
Network devices — switches, routers, firewalls (SNMP/monitoring)	`dt-obs-network-devices` (planned — not yet available)

A future macro dt-obs-network skill may connect all network concepts (devices, hosts/process/pod metrics, flows, availability monitors, cloud network monitoring). Until it exists, this skill carries the flow-specific cross-links above.

Reference Files

references/oneagent-flows/oneagent-flows.md — Validated. Data model, field reference, and DQL for the default_network_flows bucket: top talkers, traffic maps, protocol/port breakdowns, connection health (resets/timeouts/retransmissions/RTT), bandwidth in bps, and which side of a flow is the peer.
references/peer-resolution/peer-resolution.md — Validated. Shared Smartscape lookups that resolve a raw flow IP (and optional port) to a monitored host, process, Kubernetes pod, or service (host → pod → service → external). Used by both OneAgent flows and NetFlow.
references/oneagent-flows/configuration.md — Enabling and tuning builtin:network-connection-monitoring (the setting that produces OneAgent flow data).
references/netflow/netflow.md — Validated. NetFlow/IPFIX/sFlow ingested via an OpenTelemetry Collector into logs: data model, direction semantics (unidirectional, no client/server role), and DQL for top conversations/talkers/ports, protocol breakdowns, traffic-over-time, and per-exporter/per-interface views.
references/netflow/configuration.md — OTel Collector netflow-receiver ingestion path and the dedicated-bucket routing recommendation for netflow logs.
references/cloud-flows/aws/aws.md — Validated (AWS). AWS VPC Flow Logs and Transit Gateway flow logs ingested into logs: aws.vpc/aws.tgw field model (incl. pkt_srcaddr vs srcaddr, log_status filtering), and DQL for top conversations/talkers/ports, rejected-traffic (security), egress traffic_path, per-VPC/subnet/AZ, inter-VPC, traffic-over-time, and TGW packet-loss. Also AWS entity resolution — ENI/instance by id or IP-in-aws.object — for agentless resources the shared peer lookups miss.
references/cloud-flows/aws/configuration.md — Amazon Data Firehose ingestion path for AWS flow logs and the dedicated-bucket routing recommendation.

(Azure NSG/VNet and GCP VPC flow logs are not yet documented; add them as sibling cloud-flows/<provider>/ folders when tenant data is available.)

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Dt Obs Network Flows AI skill do?

Why use Dt Obs Network Flows on TypingMind?

Because you install it once and use it with any model. Dt Obs Network Flows is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Dt Obs Network Flows in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Dynatrace/dynatrace-for-ai/tree/main/skills/dt-obs-network-flows. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Dt Obs Network Flows?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Dt Obs Network Flows?

As many as you like. As long as a model supports skills, you can use Dt Obs Network Flows with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Dt Obs Network Flows AI skill free?

Yes. It is published on GitHub by Dynatrace under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Caveman Discover

JuliusBrussee

CommunityPopular

Find and label every LLM workflow in the repository so Caveman Cloud groups spend by workflow instead of one bucket. Use for "discover workflows" or breaking LLM spend down by workflow.

Caveman Manage

Inspect Caveman Cloud's experiment lifecycle and block unsafe execution. Use when asked to start, approve, cancel, promote or roll back a Caveman experiment.

Caveman Setup

Wire a repository through the Caveman Cloud gateway so every LLM request is measured, with no behavior change. Use for "set up caveman" or adding LLM spend observability.

Eng Runbook

An engineering runbook — service overview, alerts table, dashboards links, common procedures with copy-pasteable commands, on-call rotation, and an incident-response checklist. Use when the brief…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Network Flows Skill

What Network Flows Tell You

The Three Flow Sources

Routing logic

Related Network Data in Dynatrace

Reference Files

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now