[WIP] Create events table for live logs and worker name #96
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds
events
table to the broker database to store events related to arequest
. The table has 5 columns:event_id
: id of the eventevent_type
: type of the event. For exampleworker_name
,user_visible_log
,log
etc...request_uid
: the request uid of the request, this is a foreign key tosystem_request.request_uid
.message
: the content of the event.timestamp
: creation timestamp of the event.Pros and cons for the worker name info (see this PR).
Pros:
Cons:
system_request
table and is harder to access by this lineThis PR has to be merged with ecmwf-projects/cads-worker#32.