Skip to content

Conversation

Leandros
Copy link

Checklist

  • I have read the Contributor Guide
  • I have read and agree to the Code of Conduct
  • I have added a description of my changes and why I'd like them included in the section below

Description of Changes

When emitted, the span events look like this (for an imaginary function called print, taking two arguments):

ts=2025-08-29T13:29:27.488649565Z level=info target=_rsplayground span=print span_path=print message=new
ts=2025-08-29T13:29:27.488658128Z level=info target=_rsplayground span=print span_path=print message=enter arg1="hello" arg2="world"
ts=2025-08-29T13:29:27.488678624Z level=info target=_rsplayground span=print span_path=print message=exit
ts=2025-08-29T13:29:27.488694014Z level=info target=_rsplayground span=print span_path=print message=close time.busy=20.5µs time.idle=23.7µs

This allows for some more fine-grain control over what's printed when spans are entered.

The defaults are kept; therefore, existing behavior does not change (i.e this is a non-breaking change).

Related Issues

None

When emitted, the span events look like this (for an imaginary function
called `print`, taking two arguments):

    ts=2025-08-29T13:29:27.488649565Z level=info target=_rsplayground span=print span_path=print message=new
    ts=2025-08-29T13:29:27.488658128Z level=info target=_rsplayground span=print span_path=print message=enter arg1="hello" arg2="world"
    ts=2025-08-29T13:29:27.488678624Z level=info target=_rsplayground span=print span_path=print message=exit
    ts=2025-08-29T13:29:27.488694014Z level=info target=_rsplayground span=print span_path=print message=close time.busy=20.5µs time.idle=23.7µs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant