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
Is your feature request related to a problem? Please describe.
It would be really nice to have a streaming channel dedicated to tracing for wasmrs components. This would allow realtime feedback and telemetry from long running wasm components.
Propose a solution
When developing a component in rust, there should be a function that allows for tracing to be passed back to the Wick runtime. I am not sure how time should be calculated here, that may be something for Wick to handle.
...The attributes are important to be configurable by the developer.
let tracing = wick_component:start_span(span_name:String, attributes:Struct);
...tracing.send_span_event!(Log:Struct);
...tracing.end_span;//likely needs to be explicit so that wick can calculate the start and end time?
...
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered:
The foundation for this was added in #289 with the added __event FnF host operation. We need to build a tracing subscriber that propagates spans and events through that call to the host.
Is your feature request related to a problem? Please describe.
It would be really nice to have a streaming channel dedicated to tracing for wasmrs components. This would allow realtime feedback and telemetry from long running wasm components.
Propose a solution
When developing a component in rust, there should be a function that allows for tracing to be passed back to the Wick runtime. I am not sure how time should be calculated here, that may be something for Wick to handle.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: