For the complete documentation index, see llms.txt. This page is also available as Markdown.

Getting Started with DevTools

Get DevTools running and see your first HTTP/S traffic in under 5 minutes.

DevTools is a browser-based interface for real-time HTTP/S traffic inspection. Think Chrome DevTools Network tab, but for your Linux server.

  • See inside HTTPS without proxies or certificates

  • Know which process/container/pod made each request

  • Full request/response details including headers and bodies

  • No application restarts or code changes required


Prerequisites

  • Linux host with kernel 5.10+

  • Root/sudo access

  • A browser to access the DevTools UI

Verify compatibility: Run the preflight check to confirm your system supports eBPF:


Step 1: Install Qtap

This installs the qtap binary to your system path.

For manual installation, see Linux Binary Installation.

For detailed Docker setup, see Docker Container Installation.

For Kubernetes deployments, install via Helm:

For detailed Kubernetes setup, see Helm Chart Installation.


Step 2: Run with DevTools Enabled

Qtap starts capturing traffic immediately. DevTools is now accessible.

The -e ENABLE_DEV_TOOLS=true environment variable enables the DevTools UI.

If you installed with --set devtools.enabled=true, DevTools is already enabled.

Port-forward to access DevTools locally:

Replace qtap-xxxxx with your actual pod name from kubectl get pods.


Step 3: Access DevTools

Open your browser and navigate to:

You should see the DevTools interface with three tabs: Processes, Connections, and Requests.

For remote servers, use SSH port forwarding:


Step 4: Verify It Works

Generate some test traffic to confirm DevTools is capturing:

Switch to the Requests tab in DevTools. You should see:

  • The GET and POST requests to httpbin.org

  • Status codes (200)

  • The process that made the request (curl)

  • Request timing

Click on any request to see:

  • Full request headers

  • Response body

  • A copy-pasteable cURL command


Quick Tour

DevTools has three tabs:

Tab
What It Shows

Processes

Real-time inventory of all processes on the host

Connections

Network connections with process attribution

Requests

Individual HTTP transactions with full details

For a detailed walkthrough of the interface, see the DevTools Interface Guide.


Next Steps


Troubleshooting

DevTools Not Loading

  1. Check Qtap is running:

    • Binary: ps aux | grep qtap

    • Docker: docker ps | grep qtap

  2. Verify DevTools is enabled:

    • Binary: Must include --enable-dev-tools flag

    • Docker: Must include -e ENABLE_DEV_TOOLS=true

  3. Check the port:

    • Ensure nothing else is using port 10001

    • Verify with curl http://localhost:10001/devtools

No Traffic Appearing

  1. Qtap must be running BEFORE traffic is generated - Restart qtap, then make requests

  2. Check traffic direction - Default captures egress (outbound) traffic

  3. Verify the event stream is working - Check the raw API to confirm events are flowing:

You should see SSE events like event: process.started and event: connection.opened. If events are streaming but the UI is empty, try refreshing your browser.

Last updated