From 0c085acfdc58be1fbec680acaf2571849735da23 Mon Sep 17 00:00:00 2001 From: Michael Beemer Date: Fri, 23 Jan 2026 15:00:49 -0500 Subject: [PATCH 1/2] Fix br html in the observability appendix Signed-off-by: Michael Beemer --- specification/appendix-d-observability.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/specification/appendix-d-observability.md b/specification/appendix-d-observability.md index 0a35385d..f91037e2 100644 --- a/specification/appendix-d-observability.md +++ b/specification/appendix-d-observability.md @@ -61,9 +61,9 @@ Telemetry hooks can emit OpenTelemetry signals in three distinct ways: | Pattern | Advantages | Disadvantages | | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **Span Events**
![recommended](https://img.shields.io/badge/recommended-green) | - Leverages existing trace configuration and tooling
- Minimal overhead, no additional spans created
- Maintains trace context relationships
- Simpler than creating spans | - Requires an active span to function
- Must gracefully handle absence of active span
- Limited to span lifetime and context. | -| **Event Logging** | - Works independently without active spans
- Aligns with OpenTelemetry's emerging direction
- Suitable for environments without tracing
- Simpler implementation model | - Requires an event exporter to be configured
- Processed and stored separately from spans
- Event logging standards still evolving | -| **Standalone Spans** | - Distributed traces contain every evaluation
- Detailed timing information
- Full span lifecycle control | - Creates one span per evaluation
- May clutter trace visualizations
- Increased overhead and resource usage
- Potential performance impact at scale
- More complex implementation | +| **Span Events**
![recommended](https://img.shields.io/badge/recommended-green) | - Leverages existing trace configuration and tooling
- Minimal overhead, no additional spans created
- Maintains trace context relationships
- Simpler than creating spans | - Requires an active span to function
- Must gracefully handle absence of active span
- Limited to span lifetime and context. | +| **Event Logging** | - Works independently without active spans
- Aligns with OpenTelemetry's emerging direction
- Suitable for environments without tracing
- Simpler implementation model | - Requires an event exporter to be configured
- Processed and stored separately from spans
- Event logging standards still evolving | +| **Standalone Spans** | - Distributed traces contain every evaluation
- Detailed timing information
- Full span lifecycle control | - Creates one span per evaluation
- May clutter trace visualizations
- Increased overhead and resource usage
- Potential performance impact at scale
- More complex implementation | > [!NOTE] > While span events are recommended for their low overhead and ease of use, OpenTelemetry is trending toward using log-based events instead of span events. Please refer to the [OpenTelemetry Span Event Deprecation Plan][otel-span-event-deprecation-plan] for more details. From 8f3b4f279b9f63c7662612a4db2e0c579490f44a Mon Sep 17 00:00:00 2001 From: Michael Beemer Date: Fri, 23 Jan 2026 15:08:45 -0500 Subject: [PATCH 2/2] Update specification/appendix-d-observability.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Michael Beemer --- specification/appendix-d-observability.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/specification/appendix-d-observability.md b/specification/appendix-d-observability.md index f91037e2..0c2376a4 100644 --- a/specification/appendix-d-observability.md +++ b/specification/appendix-d-observability.md @@ -61,9 +61,9 @@ Telemetry hooks can emit OpenTelemetry signals in three distinct ways: | Pattern | Advantages | Disadvantages | | ---------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| **Span Events**
![recommended](https://img.shields.io/badge/recommended-green) | - Leverages existing trace configuration and tooling
- Minimal overhead, no additional spans created
- Maintains trace context relationships
- Simpler than creating spans | - Requires an active span to function
- Must gracefully handle absence of active span
- Limited to span lifetime and context. | -| **Event Logging** | - Works independently without active spans
- Aligns with OpenTelemetry's emerging direction
- Suitable for environments without tracing
- Simpler implementation model | - Requires an event exporter to be configured
- Processed and stored separately from spans
- Event logging standards still evolving | -| **Standalone Spans** | - Distributed traces contain every evaluation
- Detailed timing information
- Full span lifecycle control | - Creates one span per evaluation
- May clutter trace visualizations
- Increased overhead and resource usage
- Potential performance impact at scale
- More complex implementation | +| **Span Events**
![recommended](https://img.shields.io/badge/recommended-green) |
  • Leverages existing trace configuration and tooling
  • Minimal overhead, no additional spans created
  • Maintains trace context relationships
  • Simpler than creating spans
|
  • Requires an active span to function
  • Must gracefully handle absence of active span
  • Limited to span lifetime and context.
| +| **Event Logging** |
  • Works independently without active spans
  • Aligns with OpenTelemetry's emerging direction
  • Suitable for environments without tracing
  • Simpler implementation model
|
  • Requires an event exporter to be configured
  • Processed and stored separately from spans
  • Event logging standards still evolving
| +| **Standalone Spans** |
  • Distributed traces contain every evaluation
  • Detailed timing information
  • Full span lifecycle control
|
  • Creates one span per evaluation
  • May clutter trace visualizations
  • Increased overhead and resource usage
  • Potential performance impact at scale
  • More complex implementation
| > [!NOTE] > While span events are recommended for their low overhead and ease of use, OpenTelemetry is trending toward using log-based events instead of span events. Please refer to the [OpenTelemetry Span Event Deprecation Plan][otel-span-event-deprecation-plan] for more details.