112 packages tagged with “correlation”
A module that instruments incoming request with System.Diagnostics.Activity and notifies listeners with DiagnosticsSource.
Enrich logs with a unique ID so you can track logs for specific requests.
Provides abstractions to correlate requests between microservices.
Correlate requests between microservices using a correlation ID.
Dependency injection extensions for Correlate.
Provides capability to use correlation in applications
ASP.NET Core middleware component to correlate requests between microservices using correlation ID request headers.
CorrelatorSharp, a set of tools for adding correlation identifiers for actions performed by users and machine across your applications. Your one stop shop for context-aware logging and diagnostics.
Hangfire integration of Correlate to add correlation id support to Hangfire background/scheduled jobs.
Helpful resources for .NET Core and ASP.NET Core logging using various logger frameworks and Microsoft.Extensions.Logging.ILogger interface.
Plugin for ServiceStack that ensures there's a unique request correlation Id in header
The "Web API Correlator" enables correlation functionality for Web API and interconnected Web API services within a service composition. With the increasing complexity of modern distributed SOA systems containing interconnected services, it becomes crucial to determine causal relationships between the services and its clients. It is important to understand the various components that were part of a request flow to support critical scenarios such as health monitoring, troubleshooting, and root cause analysis. For this reason many frameworks provide correlation capability. For example, WCF has built-in correlation functionality. Although Web API creates (Request.GetCorrelationId()) and carries the Correlation Id throughout the HTTP request handling process, taking care of thread context switches as part of asynchronous nature of processing Web API requests, the boundary for this Correlation Id is limited to a single server-side request-response cycle. In other words, the Correlation Id Web API provides "out of the box" is limited to a single service boundary. In essence, Web API lacks ability to correlate processes between client and server, as well as interconnected services chains applicable to many distributed SOA applications. Effectively, we lose ability to relate multiple events immediately as a process crosses the service boundary; the information about multiple linked events within the system become dispersed data records rather representing the related nature of those events. The "Web API Correlator" enables absent functionality by transferring the Correlation Id from API Client (browser or .NET HttpClient, or .NET WebClient) to the server, propagating it into the server-side Web API process, and forwarding to interconnected Web API services within a service composition. The "Web API Correlator" contains correlation component for .NET, and offers a plugin for jQuery AJAX. The jQuery plug-in manages and maintains the Correlation Id on the client-side and ensures the Correlation Id being added to all AJAX requests.
Rebus integration of Correlate to correlate message flow via any supported Rebus transport.
Middleware facilitation for outbound HttpClient requests that is a mirror image of the functionality provided by ASP.Net Core (and OWIN) inbound request middleware.
A telemetry initializer that adds a request's authorization header
Correlation Id provider as well get correlation id where needed.
Package Description
Transform financial market price data into technical analysis indicators such as MACD, Stochastic RSI, Average True Range, Parabolic SAR, and more.
ASP.NET Core middleware processing incoming request correlation ID, together with HTTP message handler for forwarding correlation ID to subsequent requests.
Abstractions for the uniform use of Http.Correlation. Based on the primary Http header `X-Correlation-ID` as well as the alternative Http header `X-Request-ID`.