hyperlight-dev / hyperlight-dev/hyperlight

Revisit tracing strategy

Open
#188 3 comments 0 reactions 1 assignee Claimed by @devigned View on GitHub
lifecycle/confirmed
Dominant language
Rust
Stars
4.7k
Forks
208
Avg merge
1d 7h
Merged PRs (30d)
47

Description

The current state of tracing in hyperlight is a bit all over the place. We should have:

- Less fine grained tracing: Right now many irrelevant small helper functions are being traced. We should consider only covering our APIs
- Include guest calls in tracing spans
- Revisit which function parameters should and shouldn't be traced.
- Revisit tracing log levels

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.