From 28ceeebf0f5b13f2a99c7afeb2692e5c156838e4 Mon Sep 17 00:00:00 2001 From: Anatoli Babenia Date: Fri, 27 Jan 2023 21:51:44 +0300 Subject: [PATCH] Document limitations on span recording --- specification/protocol/otlp.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/specification/protocol/otlp.md b/specification/protocol/otlp.md index 4d222c4c16b..8143b3fa038 100644 --- a/specification/protocol/otlp.md +++ b/specification/protocol/otlp.md @@ -39,6 +39,7 @@ nodes such as collectors and telemetry backends. - [Implementation Recommendations](#implementation-recommendations) * [Multi-Destination Exporting](#multi-destination-exporting) - [Known Limitations](#known-limitations) + * [Span Tracking](#span-tracking) * [Request Acknowledgements](#request-acknowledgements) + [Duplicate Data](#duplicate-data) - [Future Versions and Interoperability](#future-versions-and-interoperability) @@ -643,6 +644,13 @@ speed of reception (within the available limits imposed by the size of the client-side queue). ## Known Limitations + +### Span Tracking + +It is impossible to send incomplete spans, so if the span failed to complete for +any reason (abnormal termination, exception, logical error), there won't be any +sign that the span even started. For the same reason real-time tracking of spans +is impossible. Spans are sent only when their end is reached. ### Request Acknowledgements