Define a common format for logs in Hyperlight #375

Activity

1. dblnz

   added

   lifecycle/needs-reviewThe issue has not yet been reviewed.The issue has not yet been reviewed.

   on Mar 21, 2025
2. dblnz

   added the

   Enhancement

   issue type on Mar 21, 2025
3. danbugs

   added

   lifecycle/confirmedBug is verified or proposal seems reasonableBug is verified or proposal seems reasonable

   and removed

   lifecycle/needs-reviewThe issue has not yet been reviewed.The issue has not yet been reviewed.

   on Apr 23, 2025
4. danbugs

   added this to the v0.4.0 milestone on Apr 23, 2025
5. danbugs

   assigned

   dblnz

   on Apr 23, 2025
6. danbugs

   modified the milestones: v0.4.0, v0.5.0 on Apr 23, 2025
7. danbugs

   added this to Hyperlight Milestoneson Apr 23, 2025
8. danbugs

   modified the milestones: v0.5.0, Upcoming on May 7, 2025
9. jsturtevant

   added

   good first issueGood for newcomersGood for newcomers

   help-wantedThe issue could use external help.The issue could use external help.

   on Jun 27, 2025
10. dblnz commented on Sep 10, 2025

    

    dblnz

    on Sep 10, 2025

    ContributorAuthor

    More actions

    To correctly identify each sandbox in an environment running multiple sanboxes, we should generate a UUID for each sandbox and link the logs/traces to the specific ID.
    This way it makes it simpler to follow and filter logs in a concurrent system.

    Furthermore, we should define a common format for the logs generated inside hyperlight.
    Maybe starting from something like sandbox=<UUID> message="something" and building on top of it to add other fields to make it simpler to grep/filter afterwards.
11. simongdavies commented on Sep 10, 2025

    

    simongdavies

    on Sep 10, 2025

    Member

    More actions

    Maybe starting from something like sandbox=<UUID> message="something" and building on top of it to add other fields to make it simpler to grep/filter afterwards.

    Yes , we should call this correlation_id, I think the challenge is how we propagate this value

    👍React with 👍2Reacted by Doru Blânzeanu and James Sturtevant
12. 5 remaining items

    Load more

13. devigned commented on Oct 22, 2025

    

    devigned

    on Oct 22, 2025

    Contributor

    More actions

    @dblnz, please schedule a discussion.
14. dblnz

    modified the milestones: v0.11.0, v0.12.0 on Oct 28, 2025
15. dblnz

    added sub-issues on Nov 25, 2025

    • Use tracing crate instead of log to create logs #1028
    • Create example for correlation ID propagation down to hyperlight calls #1029
    • Change the logs format #1030
    • Analyze codebase and ensure logs/traces level is appropriate #1031
    • Revisit tracing strategy #188
16. dblnz

    modified the milestones: v0.12.0, v0.13.0 on Dec 8, 2025
17. vshailesh commented on Jan 25, 2026

    

    vshailesh

    on Jan 25, 2026

    Contributor

    More actions

    @dblnz I can pick some small part of these issues, and something more when I get more familiar.
18. dblnz commented on Jan 27, 2026

    

    dblnz

    on Jan 27, 2026

    ContributorAuthor

    More actions

    @dblnz I can pick some small part of these issues, and something more when I get more familiar.

    Hey @vshailesh so, I think #1028, #1030 and #1029 should be doable.

    👀React with 👀1Reacted by Shailesh
19. jsturtevant

    modified the milestones: v0.13.0, Upcoming on Feb 18, 2026
20. jsturtevant commented on Feb 18, 2026

    

    jsturtevant

    on Feb 18, 2026

    Contributor

    More actions

    since this is a tracking feature moved it to upcoming and we can move the individual features into the releases as they are worked on

    👍React with 👍1Reacted by Doru Blânzeanu