You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Today span limits are set automatically when importing the trace SDK module here
It's not possible to change these limits once set. As a result, the only way to set them today is through environment variables and the env vars must be set before the trace module is imported.
We should change it so that the trace SDK configures the limits lazily and allows users to pass in limits programmatically. Something like the following should work I think.
# new SpanLimits type in APIclassSpanLimit:
def__init__(self, events=None, links=None, attributes=None):
self.events=_get_span_limits_from_env("events", default=events)
self.links=_get_span_limits_from_env("links", default=links)
self.attributes=_get_span_limits_from_env("attributes", default=attributes)
Tracer provider will accept an optional SpanLimits instance and pass it forward to spans via tracer. Each span can then initiate it's collection objects with the specified limits.
Today span limits are set automatically when importing the trace SDK module here
It's not possible to change these limits once set. As a result, the only way to set them today is through environment variables and the env vars must be set before the trace module is imported.
We should change it so that the trace SDK configures the limits lazily and allows users to pass in limits programmatically. Something like the following should work I think.
Tracer provider will accept an optional SpanLimits instance and pass it forward to spans via tracer. Each span can then initiate it's collection objects with the specified limits.
Usage would look like:
The text was updated successfully, but these errors were encountered: