Does setting span status to Error automatically create span event? about opentelemetry.io HOT 8 CLOSED

@avillela can you take a look at your blog post and figure out if the sentence can be rephrased to match what is discussed here. As a quick fix, I am also OK with removing the sentence entirely.

Thanks everyone. From the response so far it seems safe to say that various SDKs and instrumentations may automatically collect span exception events when setting the span status to ERROR, but we (specifically our vendor platform) should not make this assumption, correct?

That's my understanding as well, yes.

from opentelemetry.io.

Thanks for raising this @cheempz!

@reese-lee @avillela can you verify if this is somewhere defined in the spec and just not available in Python, or if this is not in the spec?

If it is in the spec, we can raise an issue with python or check if one exists already and close this issue
If it is not in the spec, let's remove that sentence from the blog post. Although we try to avoid changing blog posts after publication, I think it would be justified in this case to avoid future confusion.

from opentelemetry.io.

@open-telemetry/python-approvers if someone can take a look and help with answering this question, this would be great/can help to expedite the investigation

from opentelemetry.io.

I don't think we have that kind of magic in Python other than sdk's Span constructor will add to the span every event it get passed to it. Span.record_exception will add the exception as event automatically, maybe they meant that?

from opentelemetry.io.

It's a convention in instrumentations to create a span event with a stack trace (or other error details), so that may be what was referred to? There's nothing inherent in OTel SDKs that create a span event automatically, though.

from opentelemetry.io.

Apologies - I think the wording we used might have been a bit confusing.

From my understanding in Python, if you have:

with tracer.start_as_current_span("do_roll", set_status_on_exception=True)

and your span throws an exception, then that span will be marked as an error span.

I believe that tracks with the above comments? If so, I'm happy to modify that sentence in the blog post to clarify the confusion.

from opentelemetry.io.

Thanks everyone. From the response so far it seems safe to say that various SDKs and instrumentations may automatically collect span exception events when setting the span status to ERROR, but we (specifically our vendor platform) should not make this assumption, correct?

from opentelemetry.io.

Closing as completed by #4844.

from opentelemetry.io.