Track Amazon EventBridge operations in your test diagrams. This extension intercepts PutEvents, rule management, target management, event bus lifecycle, and other EventBridge API calls via the AWS SDK HTTP pipeline.

NuGet Package: Kronikol.Extensions.EventBridge
Namespace: Kronikol.Extensions.EventBridge
Since: v2.20.0

Using a shared library or abstraction layer? If your code doesn't use the EventBridge SDK directly — e.g. it goes through a shared event-routing library, wrapper, or custom abstraction — this extension won't be able to intercept the underlying calls. See Tracking Custom Dependencies for alternative approaches including MessageTracker and TrackingProxy<T>.

using Amazon.EventBridge;
using Kronikol.Extensions.EventBridge;

var config = new AmazonEventBridgeConfig
{
    RegionEndpoint = RegionEndpoint.USEast1
};

config.WithTestTracking(new EventBridgeTrackingMessageHandlerOptions
{
    CurrentTestInfoFetcher = CurrentTestInfo.Fetcher
});

var client = new AmazonEventBridgeClient(credentials, config);

Amazon EventBridge uses JSON-RPC over HTTP POST — all requests go to the same endpoint with the operation identified by the X-Amz-Target header (e.g. AWSEvents.PutEvents). This is the same pattern used by DynamoDB.

The extension plugs a DelegatingHandler into the AWS SDK's HTTP pipeline via AmazonEventBridgeConfig.HttpClientFactory. Every HTTP request/response is intercepted, classified, and logged to RequestResponseLogger for diagram generation.

This follows the exact same AWS SDK interception pattern as the Integration S3 Extension, Integration DynamoDB Extension, Integration SQS Extension, and Integration SNS Extension extensions.

var config = new AmazonEventBridgeConfig
{
    RegionEndpoint = RegionEndpoint.USEast1
};

var options = new EventBridgeTrackingMessageHandlerOptions
{
    ServiceName = "EventBridge",
    CallerName = "OrderService",
    Verbosity = EventBridgeTrackingVerbosity.Detailed,
    CurrentTestInfoFetcher = CurrentTestInfo.Fetcher
};

config.WithTestTracking(options);
var client = new AmazonEventBridgeClient(credentials, config);

public class MyWebAppFactory : WebApplicationFactory<Program>
{
    protected override void ConfigureWebHost(IWebHostBuilder builder)
    {
        builder.ConfigureServices(services =>
        {
            services.PostConfigure<EventBridgeTrackingMessageHandlerOptions>(opts =>
            {
                opts.CurrentTestInfoFetcher = CurrentTestInfo.Fetcher;
            });
        });
    }
}

v2.23.0+ Dual-Resolution: EventBridgeTrackingMessageHandler accepts an optional IHttpContextAccessor? httpContextAccessor constructor parameter for resolving test identity from HTTP request headers when running inside the SUT's request pipeline. v2.26.3+: Set HttpContextAccessor on EventBridgeTrackingMessageHandlerOptions instead — the tracker reads it automatically. See HTTP Tracking Setup#Dual-Resolution Test Identity (v2.23.0+) for details.

• TagResource, UntagResource, ListTagsForResource — noisy tag management
• ListEventBuses — infrastructure query with low diagram value

Authorization, x-amz-date, x-amz-security-token, x-amz-content-sha256, User-Agent, amz-sdk-invocation-id, amz-sdk-request

Full HTTP details — method is POST, URI is the actual AWS endpoint, all request/response bodies and non-excluded headers logged.

Classified labels with contextual detail:

• PutEvents [OrderCreated] — includes DetailType from first entry
• PutEvents [OrderCreated] x5 — includes entry count when > 1
• PutEvents x3 — entry count without DetailType
• PutRule my-rule — includes rule name
• DeleteRule old-rule
• CreateEventBus orders-bus — includes bus name
• Other operations: enum name (e.g. ListRules, StartReplay)

URI: eventbridge://{busName}/ (defaults to eventbridge://default/ when no bus name)

Grouped, minimal labels:

• PutEvents
• ManageRule (PutRule, DeleteRule)
• ManageTargets (PutTargets, RemoveTargets)
• ManageBus (CreateEventBus, DeleteEventBus)
• Other: enum name

No request/response bodies or headers logged. Other operations are skipped entirely.

The classifier recognises 28 EventBridge API operations via X-Amz-Target:

Unrecognised targets map to EventBridgeOperation.Other.

For PutEvents, the classifier parses the JSON body to extract:

• EventBusName — from top-level or first entry
• DetailType — from first entry (e.g. "OrderCreated")
• Source — from first entry (e.g. "my.service")
• EntryCount — number of entries in the batch (max 10 per API call)

For PutRule, DeleteRule, DescribeRule, it extracts:

• Name → RuleName
• EventBusName

Body parsing is best-effort — malformed JSON is silently ignored.

EventBridgeTrackingMessageHandler implements ITrackingComponent and auto-registers with TrackingComponentRegistry in its constructor. This enables unused-component diagnostic warnings (passive, since v2.3.0).

This extension covers the Amazon EventBridge service (AWSSDK.EventBridge). The following are separate AWS services with their own SDK clients and are not covered:

• EventBridge Pipes (AWSSDK.Pipes)
• EventBridge Scheduler (AWSSDK.Scheduler)

• Integration S3 Extension — same AWS SDK DelegatingHandler pattern
• Integration DynamoDB Extension — same X-Amz-Target JSON-RPC classification
• Integration SQS Extension — same AWS SDK pattern
• Integration SNS Extension — same AWS SDK pattern