Skip to main content

Automation with Claude

Traffic and Flow Diagram Automation with Claude

From ping and traceroute evidence to an approved, versioned flow diagram.

0:00 / 0:00
  • Instructor-led training: Online or Destination
  • 3 days · 24 hours
  • Starts in about 3 weeks
  • Flexible and customizable

What you will be able to do

  • Explain what ping and traceroute can and cannot prove about a traffic path, and encode those limits in the diagram
  • Set up Claude Code, the Claude Agent SDK and an MCP server that exposes read-only probe tools for this workflow
  • Build deterministic Python probe runners that return typed path records Claude consumes through tool use and structured JSON outputs
  • Enrich hops with F5, Citrix NetScaler, Radware Alteon, other load balancers (Anaya LB) and Cisco APIC context, and render evidence-linked Mermaid diagrams
  • Publish diagrams to ServiceNow and GitHub behind scope limits, named approvals and an audit log, and detect path drift on a schedule

Table of contents

  1. 1What a flow diagram must prove, and what probes can tell you
  2. 2Setting up Claude Code, the Agent SDK and MCP for this workflow
  3. 3Deterministic probe runners in Python
  4. 4Path evidence model and structured outputs
  5. 5Enriching hops with load balancer context
  6. 6Data centre fabric and cloud path context
  7. 7Generating the traffic and flow diagram with Mermaid
  8. 8Guardrails, approvals and audit for probing and publishing
  9. 9Publishing to ServiceNow and GitHub
  10. 10Drift detection and scheduled re-mapping
  11. 11Capstone: request to approved flow diagram, end to end