-
Notifications
You must be signed in to change notification settings - Fork 563
Description
Contact Details [Optional]
No response
Feature Description
We recently introduced a new LoggingContext class. Creating a LoggingContext now requires an existing LogsResponse (i.e., a log record already persisted in the database).
In previous versions, we started emitting logs before the corresponding LogsResponse existed in the DB. That allowed us to capture early logs from processes like snapshot creation and image building, and persist them once the DB record was created.
With the new requirement, logs emitted during these “pre-DB” phases are currently dropped, because we can’t instantiate LoggingContext yet.
What we need
Update the logging flow so that logs emitted before LogsResponse creation are still captured and persisted. This may require implementing dedicated endpoints to create and manage logs independently of other resources.
Further considerations
We need to handle the metadata around the Origin as well.
Problem or Use Case
No response
Proposed Solution
No response
Alternatives Considered
No response
Additional Context
No response
Priority
None
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
Type
Projects
Status