Skip to main content
Version: Next

OpenTelemetry

Modular Pipelines emits traces and metrics through the standard .NET ActivitySource and Meter APIs. Add the optional integration package to connect that instrumentation to an OpenTelemetry collector:

dotnet add package ModularPipelines.OpenTelemetry

Register the instrumentation and the OTLP exporter when creating the pipeline:

using ModularPipelines;
using ModularPipelines.Extensions;

var builder = Pipeline.CreateBuilder();

builder.AddOpenTelemetry(openTelemetry => openTelemetry.AddOtlpExporter());

The exporter uses the standard OTEL_EXPORTER_OTLP_* environment variables. For example, set OTEL_EXPORTER_OTLP_ENDPOINT to the collector endpoint.

The trace and metric providers start when the pipeline is built. When the pipeline is disposed, both providers are flushed before their exporters are shut down.

Traces​

Each run creates a Pipeline.Run root span. Module spans are its children, and commands executed by a module create command child spans. Command spans include the tool, exit code, and duration. Arguments use the same secret obfuscation as command logs, so registered secrets are not exported.

The integration subscribes to these activity sources:

  • ModularPipelines
  • ModularPipelines.Modules
  • ModularPipelines.Commands

Metrics​

The ModularPipelines meter publishes:

  • modular_pipelines.module.duration — module duration in seconds
  • modular_pipelines.modules.failed — failed module count
  • modular_pipelines.module.retries — module retry count

Module metrics include module type and status attributes.

Resource attributes​

The pipeline application name becomes the OpenTelemetry service name. On common CI providers, the integration also maps the commit environment variable (for example, GITHUB_SHA or CI_COMMIT_SHA) to vcs.ref.head.revision.

Exporter registration is optional. Without AddOtlpExporter, you can add another exporter by registering it through the normal OpenTelemetry services.