Qyl.OpenTelemetry.SemanticConventions.SourceGeneration 3.4.0

Qyl.OpenTelemetry.SemanticConventions.SourceGeneration

Roslyn source generator for OpenTelemetry semantic-convention constants, descriptors, and thin helper APIs. It does not collect telemetry. Consumers own their Meter, ActivitySource, Logger, instrumentation scope, versioning, and enablement.

Use

using Qyl.OpenTelemetry.SemanticConventions.SourceGeneration;

[SemanticConventionAttributes("http")]
internal static partial class HttpAttributes;

[SemanticConventionIncubatingAttributes("http")]
internal static partial class HttpIncubatingAttributes;

[SemanticConventionMetrics("http.server")]
internal static partial class HttpServerMetrics;

[SemanticConventionIncubatingEvents("session")]
internal static partial class SessionEvents;

[SemanticConventionMeters("http.server")]
internal static partial class HttpServerMeters;

[SemanticConventionActivities("http")]
internal static partial class HttpActivityExtensions;

// Generated:
//   public const string AttributeHttpRequestMethod = "http.request.method";
//   public static partial class HttpServerRequestDurationDescriptor { ... }
//   public readonly record struct SessionStartPayload { ... }
//   public static Histogram<double> CreateHttpServerRequestDurationHistogram(this Meter meter)
//   public static Activity SetHttpRoute(this Activity activity, string value)

Generator surfaces

All five source generators use the same Roslyn shape: publish stable and incubating marker attributes during post-initialization, discover annotated partial classes with ForAttributeWithMetadataName, extract the requested semantic-convention prefix into a marker model, then emit source from the matching registry projection.

The marker attributes are themselves generated via RegisterPostInitializationOutput; no runtime dependency is added by consuming this package. The events generator also emits SemanticConventionEvents.IsExternalInit.g.cs so generated record structs work on older target frameworks.

Stable markers emit stable rows plus deprecated migration symbols. Incubating markers are supersets: stable + development/alpha/beta/release-candidate + deprecated. This mirrors Java/Python's incubating package behavior and avoids breaking consumers when conventions are promoted.

Choose one projection per prefix in normal consumer code. Incubating is a superset, so declaring both stable and incubating meter/activity helpers for the same prefix in the same namespace can make shared extension methods ambiguous. If a test fixture intentionally declares both, call the generated static helper class explicitly.

Event rows do not currently carry a stable ActivityEvent-vs-Logger/Event discriminator. The generator emits event names and payload structs; the caller chooses the emission API at use-site. If upstream adds a discriminator later, the event emitter has a single routing point for that field.

Versioning

Tracks two source registries:

The GenAI registry is development-stage. It is pinned by commit SHA and must not be presented as a stable v1.42.0 release.

The embedded registry is regenerated by scripts/generate.sh with Weaver v0.24.2. The script runs Weaver twice, once for core and once for GenAI, then merges the qyl-owned projections while preserving per-row source metadata. The core run strips the scopes that moved out of core in the 1.42 migration boundary (gen-ai, mcp, openai, and aws-bedrock) so those rows come only from the GenAI source.

The generated member shape is snapshot-tested per stability tier. Full-surface consumer smoke builds cover net472, netstandard2.0, net6.0, net8.0, net9.0, and net10.0.

Licensed under MIT (qyl); generated content is derived from OpenTelemetry semantic conventions, Apache-2.0.