-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
limit number of log events #46
Comments
Yes. Thanks. |
RaduBerinde
added a commit
to RaduBerinde/lightstep-tracer-go
that referenced
this issue
Sep 29, 2016
Basictracer now supports a `MaxLogPerSpan` options; plumbing this option in Lightstep as well. Fixes lightstep#46.
RaduBerinde
added a commit
to RaduBerinde/lightstep-tracer-go
that referenced
this issue
Sep 30, 2016
Basictracer now supports a `MaxLogPerSpan` option; plumbing this option in Lightstep as well. Fixes lightstep#46.
RaduBerinde
added a commit
to RaduBerinde/lightstep-tracer-go
that referenced
this issue
Sep 30, 2016
Basictracer now supports a `MaxLogPerSpan` option; plumbing this option in Lightstep as well. Fixes lightstep#46.
bhs
pushed a commit
that referenced
this issue
Oct 1, 2016
Basictracer now supports a `MaxLogPerSpan` option; plumbing this option in Lightstep as well. Fixes #46.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We had an issue where a bug was causing endless retries and the memory inside basictracer grew indefinitely. It would be great if there was an option to only keep the last
X
log events inside a span.Assuming we implement this functionality in basictracer, would it be ok with lightstep to pass along that option? (similar to how we pass
DropSpanLogs
)The text was updated successfully, but these errors were encountered: