Skip to content

Excluding Requests

Aryeh Citron edited this page Apr 17, 2026 · 3 revisions

Excluding Individual Requests

To exclude a specific HTTP request from appearing in the diagram, add the test-tracking-ignore header:

var request = new HttpRequestMessage(HttpMethod.Get, "/health");
request.Headers.Add("test-tracking-ignore", "true");
await client.SendAsync(request);

Any request carrying this header will still be sent normally but will be filtered out of the diagram generation pipeline.

How It Works

When TestTrackingMessageHandler sees the test-tracking-ignore header, it sets TrackingIgnore = true on the RequestResponseLog entry. The diagram generator then filters out any logs with TrackingIgnore = true.

The header is defined as a constant: TestTrackingHttpHeaders.Ignore ("test-tracking-ignore").

Excluding Headers from Diagram Notes

To hide specific HTTP headers from appearing in diagram notes (e.g. authorization tokens), use the ExcludedHeaders property on ReportConfigurationOptions:

new ReportConfigurationOptions
{
    ExcludedHeaders = ["Authorization", "X-Api-Key", "X-Request-Id"]
}

These are combined with the built-in defaults (Cache-Control, Pragma). See Report Configuration.

Request vs Event Tracking

Tracked interactions have a RequestResponseMetaType that controls how they appear in diagrams:

Meta type Visual When used
Default Standard sequence diagram arrow HTTP requests tracked by TestTrackingMessageHandler
Event Blue note-style annotation Non-HTTP events tracked by MessageTracker (Kafka, Service Bus, etc.)

See Event Annotations for details on tracking non-HTTP interactions.

Home


Demo


Getting Started

Common Tasks

Integration Guides

Extensions

Configuration

Features

Reference

Clone this wiki locally