nexus-labs-automation

network-tracing

@nexus-labs-automation/network-tracing
nexus-labs-automation
98
8 forks
Updated 1/18/2026
View on GitHub

Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.

Installation

$skills install @nexus-labs-automation/network-tracing
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathskills/network-tracing/SKILL.md
Branchmain
Scoped Name@nexus-labs-automation/network-tracing

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

skills list

Skill Instructions


name: network-tracing description: Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues. triggers:

  • "correlate backend traces"
  • "distributed tracing"
  • "network performance"
  • "slow API calls"
  • "trace requests"
  • "track API requests" priority: 2

Network Tracing

Measure API requests and correlate with backend traces.

What to Capture (OTel-Compatible Names)

AttributeOTel NamePurpose
Methodhttp.request.methodGET, POST, etc.
Statushttp.response.status_codeSuccess/failure
URLurl.pathEndpoint (sanitized)
Durationhttp.request.durationRequest time (ms)
Sizehttp.response.body.sizePayload bytes

Using OTel naming = easier migration when OTel mobile matures. See references/otel-mobile.md for rationale.

Distributed Tracing

Propagate trace context to backend:

Client Request
    │
    ├── traceparent: 00-{trace_id}-{span_id}-01
    ├── X-Request-Id: {uuid}
    └── X-Session-Id: {session}
         │
         ▼
    Backend (correlates logs with trace_id)

Key Thresholds

MetricGoodAcceptablePoor
API p50<500ms<1s>1s
API p95<2s<5s>5s
Error rate<1%<3%>3%

Integration Options

Choose based on existing vendor:

VendoriOSAndroidApproach
SentryAuto URLSession swizzlingOkHttp integrationAutomatic
DatadogURLSession delegateOkHttp interceptorSemi-auto
EmbraceAuto-instrumentationAuto-instrumentationAutomatic
CustomManual interceptorManual interceptorManual

Automatic (swizzling): Less code, may miss custom clients Manual (interceptors): More control, works with any HTTP client

Platform Integration Points

PlatformManual OptionWorks With
iOSURLSession delegateAll URLSession-based clients
iOSAlamofire EventMonitorAlamofire
AndroidOkHttp InterceptorOkHttp, Retrofit
AndroidKtor HttpClientPluginKtor
RNfetch wrapperNative fetch
RNaxios interceptoraxios

Implementation

See references/mobile-challenges.md (Client-Backend Correlation) for:

  • W3C trace header format
  • Platform-specific interceptor code
  • Backend log correlation patterns

See references/performance.md (Network section) for latency budgets.