.NET and Serilog Structured Event Analytics

Implementation evidence

.NET and Serilog Structured Event Analytics: from boundary to verified row

Use .NET and Serilog Structured Event Analytics at a controlled application boundary, keep the event contract small, and verify a known outcome before building aggregate views.

1
Choose the outcome
ASP.NET API monitoring
2
Define the contract
route_template, method, status_code, and status
3
Instrument the boundary
Keep detailed exceptions in Serilog while sending a controlled error_type to Telemetry.
4
Verify the evidence
Exercise a known fixture, then inspect api_request_completed for one correctly typed terminal row.

Before you start

Prerequisites and boundaries

A server-side TELEMETRY_API_KEY
Named ASP.NET endpoints
An HttpClient with a short timeout

Delivery setup

Install and initialize server-side

Use one shared HttpClient with a server-side key, a short timeout, and a small allowlisted Log API wrapper. Keep ingestion credentials out of browser bundles, client-visible environment variables, source control, logs, and exception messages.

1Prepare one reusable server-side delivery client with bounded network behavior.
2Add the outcome event at the success, failure, retry, or timeout boundary.
3Send controlled fixtures and inspect the stored rows before enabling an alert.

Snippet

Start with one structured event

Add this shape where the workflow completes, fails, or retries. Then build the dashboard from real fields.

dotnet-serilog

.NET and Serilog Structured Event Analytics event

csharp

await telemetryClient.LogAsync("api_request_completed", new {
    route_template = context.GetEndpoint()?.DisplayName ?? "unmatched",
    method = context.Request.Method,
    status_code = context.Response.StatusCode,
    status = context.Response.StatusCode >= 500 ? "failed" : "success",
    latency_ms = stopwatch.Elapsed.TotalMilliseconds,
    trace_id = Activity.Current?.TraceId.ToString(),
    release = configuration["APP_RELEASE"]
});

Event contract

route_template, method, status_code, and status

latency_ms, trace_id, error_type, and dependency

environment, release, and safe tenant identifiers

Implementation checkpoints

Checkpoint 1

Keep detailed exceptions in Serilog while sending a controlled error_type to Telemetry.

Checkpoint 2

Read the matched endpoint route pattern rather than Request.Path.

Checkpoint 3

Propagate Activity trace identifiers for correlation without duplicating spans.

Verification

Prove the event arrived

Run this after exercising known success and failure cases. Replace the fallback table name if your final event contract differs from the snippet.

dotnet-serilog-verification

.NET and Serilog Structured Event Analytics verification query

sql

SELECT *
FROM api_request_completed
ORDER BY timestamp_utc DESC
LIMIT 20;

Confirm one terminal row per logical outcome, with the expected status, identifiers, units, and UTC time.

Inspect the inferred schema and verify that retries do not change field types or generate a new logical event ID.

Search the stored fields for credentials, raw payloads, prompts, private content, and unbounded error messages.

Exercise a provider timeout, ingestion rejection, and process shutdown before treating the dashboard as complete.

Implementation references

Review the event contract, data-safety guidance, and upstream primary documentation before enabling a new production path.

Canonical wide events Dependency latency SQL Serilog for ASP.NET Core

Production boundary

Keep the outcome event small and recoverable

This pattern provides

A bounded, SQL-ready outcome beside the upstream workflow.
Stable fields for dashboards, alerts, and cross-event correlation.
A fixture-driven path for validating success, failure, retry, and timeout behavior.

This pattern does not provide

An OTLP exporter, automatic collection pipeline, or replacement for detailed traces and diagnostic logs.
Exactly-once delivery merely because the payload contains an event ID.
Permission to collect raw provider payloads, user content, credentials, or regulated data.

Delivery and idempotency Batching and shutdown Troubleshoot ingestion

Event schema starting points

Review the row grain, emit boundary, required types, privacy classes, example payload, and validation checklist before adapting a query or snippet to production.

API reliability10 fields