Class DigitalOceanHostApplicationBuilderExtensions
Namespace: Cephalon.Observability.DigitalOcean.Hosting
Assembly: Cephalon.Observability.DigitalOcean.dll
Adds DigitalOcean-hosted observability defaults and collector wiring for Cephalon hosts.
public static class DigitalOceanHostApplicationBuilderExtensionsInheritance
Section titled “Inheritance”object ← DigitalOceanHostApplicationBuilderExtensions
Inherited Members
Section titled “Inherited Members”object.Equals(object?), object.Equals(object?, object?), object.GetHashCode(), object.GetType(), object.MemberwiseClone(), object.ReferenceEquals(object?, object?), object.ToString()
Methods
Section titled “Methods”AddCephalonDigitalOcean<TBuilder>(TBuilder, Action<DigitalOceanTelemetryExportOptions>?)
Section titled “ AddCephalonDigitalOcean<TBuilder>(TBuilder, Action<DigitalOceanTelemetryExportOptions>?)”Adds DigitalOcean-aware OpenTelemetry registration for the Cephalon engine diagnostics surface.
public static TBuilder AddCephalonDigitalOcean<TBuilder>(this TBuilder builder, Action<DigitalOceanTelemetryExportOptions>? configure = null) where TBuilder : IHostApplicationBuilderParameters
Section titled “Parameters”builder TBuilder
The target host-application builder.
configure Action<DigitalOceanTelemetryExportOptions>?
An optional callback that can extend or override the configuration-driven DigitalOcean telemetry export options.
Returns
Section titled “Returns”TBuilder
The same builder instance for fluent host composition.
Type Parameters
Section titled “Type Parameters”TBuilder
The host-application builder type to extend.
Remarks
Section titled “Remarks”
This package keeps DigitalOcean-specific collector selection, best-effort Droplet metadata defaults,
and hosted resource defaults outside Cephalon.Engine and the baseline observability package.
It still uses the shared Engine:Observability:Telemetry contract so hosts can keep one explicit
telemetry surface.
When Endpoint or UseSelfHostedDefaults is configured, the package keeps using the shared
collector-oriented OTLP path and layers DigitalOcean resource defaults on top. When those shared endpoint
settings are absent and UseInClusterCollectorService is enabled, the package resolves an explicit
in-cluster service endpoint for DOKS deployments so collector-first DigitalOcean setups stay explicit
without over-claiming a managed DigitalOcean OTLP exporter path.