Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add separate timestamp for factory-generated events #24

Open
jclulow opened this issue May 1, 2023 · 0 comments
Open

add separate timestamp for factory-generated events #24

jclulow opened this issue May 1, 2023 · 0 comments

Comments

@jclulow
Copy link
Collaborator

jclulow commented May 1, 2023

The time_remote field on the job event record was added to store the local time provided by the agent when it generated the record. This is distinct from the original time field, which reflects the time at which the buildomat core server received the event from the agent.

Once factories were added, new event record types were added that are not generated on the agent but rather within the factory; e.g., information about the IPMI state of the machine, or output from the machine's serial console. The time in this case comes from the factory, and is thus also distinct from the time on the agent and the time on the core server.

We should add an optional time_factory column to store these timestamps for factory-provided events, and stop using time_remote in that case, leaving time_remote to the agent itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant