Skip to content

Revisit tracing strategy #188

Open
Open

Description

@ludfjig

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

Activity

  1. added
    lifecycle/confirmedBug is verified or proposal seems reasonable
    and removed on Feb 5, 2025
  2. added this to the Backlog milestone on Mar 4, 2025
  3. simongdavies commented on Mar 19, 2025

    @simongdavies
    Member

    I suggest that we only place trace attributes on pub functions, that should reduce the overhead/noise

  4. danbugs commented on Mar 19, 2025

    @danbugs
    Contributor

    Related to #318

  5. modified the milestones: Backlog, Upcoming on Mar 19, 2025
  6. modified the milestones: Upcoming, v0.4.0 on Apr 9, 2025
  7. modified the milestones: v0.4.0, v0.5.0 on Apr 23, 2025
  8. self-assigned this
    on May 7, 2025
  9. modified the milestones: v0.5.0, v0.6.0, v0.7.0, Upcoming on Jun 4, 2025
  10. dblnz commented on Nov 25, 2025

    @dblnz
    Contributor

    I think a better parent for this issue is #375

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

lifecycle/confirmedBug is verified or proposal seems reasonable

Type

Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions