DOCSEARCHbyAlgolia
Submit Docs

Arcus Observability

website·Indexed 32 days ago

https://observability.arcus-azure.net/

A framework and set of libraries for implementing observability in .NET applications, featuring a Serilog sink for Azure Application Insights. Arcus provides tools for service-to-service correlation across Web APIs and Azure Service Bus, telemetry enrichment, telemetry filtering, and tracking for Azure dependencies including Blob Storage, Cosmos DB, Event Hubs, and Key Vault. Supports versions v2.6.0 through v3.0.0.

Tokens
108.2K
Snippets
575
Records
623
Agent score
57%

What's inside Arcus

  1. Overview of Arcus Observability

    v2.6.0
    Arcus Observability (v2.6.0) simplifies working with Azure Application Insights telemetry by leveraging the standard ILogger infrastructure. It supports tracking dependencies, requests, events, and metrics, and allows for telemetry filtering via Serilog filters and enrichment with custom correlation.

  2. Overview of Arcus Observability

    v2.7.0
    Arcus Observability (v2.7.0) integrates Azure Application Insights telemetry with the common ILogger infrastructure. It allows developers to track dependencies, log custom metrics, and log multi-dimensional telemetry data. The library supports various telemetry types including requests, events, and metrics, and provides compatibility with Serilog filters and custom correlation enrichment.

  3. Overview of Arcus.Observability features

    v2.1

    Arcus.Observability provides a suite of tools for enhancing application telemetry, including:

    • Contextual Telemetry: Simplifies providing contextual information to make telemetry more powerful.
    • Telemetry Types: Extends ILogger to support Dependencies, Events, Requests, and Metrics beyond standard logs.
    • Correlation: Provides a common set of correlation levels.
    • Telemetry Enrichment: A set of enrichers to improve the quality and detail of telemetry information.
    • Telemetry Filters: Tools to control the flow of telemetry data.
    • Sinks: Support for flowing Traces, Dependencies, Events, Requests, and Metrics into Azure Application Insights.

  4. Overview of Arcus Observability

    v2.5.0
    Arcus Observability is a library designed to simplify working with Azure Application Insights telemetry. It allows developers to use the standard ILogger infrastructure to write multi-dimensional telemetry data without manually managing logging, correlation, or tracking. The library supports various telemetry types, including dependencies, requests, events, and metrics, and integrates with Serilog for filtering and custom correlation enrichment.

  5. Overview of Arcus Observability

    v2.8.0
    Arcus Observability (v2.8.0) integrates Azure Application Insights telemetry with the common ILogger infrastructure. It allows developers to track dependencies, log custom metrics, and record multi-dimensional telemetry data. The library supports various telemetry types including requests, events, and metrics, and integrates with Serilog for filtering and custom correlation enrichment.

  6. Overview of Arcus Observability packages

    Arcus Observability provides a set of NuGet packages to kickstart observability solutions. It distinguishes between logging and telemetry (traces and metrics), providing a central point of contact via the IObservability interface facade. There are two primary backend implementations:

    1. Arcus.Observability.Telemetry.OpenTelemetry: A flexible implementation for various observability backends.
    2. Arcus.Observability.Telemetry.Serilog.Sinks.ApplicationInsights: Specifically designed for Azure Application Insights.

  7. Overview of Arcus Observability

    Arcus Observability is a collection of NuGet packages (Arcus.Observability.*) designed to abstract away boilerplate code required for tracking telemetry in applications. It minimizes infrastructure code within the implementation layer and provides developers with a consistent, extensible API that remains compatible across different observability backends and multi-dimensional contexts.

  8. Overview of Arcus Observability

    v3.0.0
    Arcus Observability (v3.0.0) simplifies working with Azure Application Insights telemetry by leveraging the standard ILogger infrastructure. It allows developers to track dependencies, log custom metrics, and record multi-dimensional telemetry data. The library supports various telemetry types (dependencies, requests, events, metrics) and integrates with Serilog for filtering and custom correlation enrichment.

  9. Understand service-to-service correlation in Arcus

    v2.7.0
    Service-to-service correlation allows developers to track a single business transaction as it moves across different application components. This ensures that the relationship between components—such as an API call triggering an Azure Service Bus message, which is then processed by a message pump—is preserved. When implemented, these relationships are visualized in the Application Insights end-to-end transaction view, helping to identify performance bottlenecks, failures, and resource usage.

  10. Understand service-to-service correlation in Arcus

    v2.6.0
    Service-to-service correlation tracks a single business transaction as it moves across different application components. It ensures that the relationship between components—such as an API call triggering an Azure Service Bus message, which is then processed by a message pump—is preserved. This allows developers to visualize the entire end-to-end transaction flow in the Application Insights transaction view, helping to identify performance bottlenecks and failures across architectural boundaries.

  11. Understand Arcus service-to-service correlation IDs

    v2.8.0

    Arcus uses three types of correlation IDs to link telemetry across different services in an Azure Service Bus solution. These IDs are passed between services via Azure Service Bus message application properties:

    • Transaction ID: A constant ID that describes the entire end-to-end transaction. All telemetry for the full flow is tracked under this ID.
    • Operation ID: Describes a single operation within a specific service. It links all telemetry generated within that individual service together.
    • Operation Parent ID: Creates the parent/child relationship between services. When Service A calls Service B, Service A becomes the 'parent', and this ID allows the system to track the dependency chain.

  12. Understand service-to-service correlation in Arcus

    v3.0.0
    Service-to-service correlation tracks relationships between separate application components involved in a single business transaction. It ensures that telemetry remains linked as a request moves across application borders—for example, from an API call to an Azure Service Bus message, and then to a message pump or Azure Function. This allows developers to view the entire transaction flow in the Azure Application Insights end-to-end transaction view, helping to identify performance bottlenecks and architectural failures.