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

Serval Build Log #570

Open
johnml1135 opened this issue Dec 11, 2024 · 0 comments
Open

Serval Build Log #570

johnml1135 opened this issue Dec 11, 2024 · 0 comments

Comments

@johnml1135
Copy link
Collaborator

johnml1135 commented Dec 11, 2024

Option 1 - build log

Add it to the Build repo structure add a field called ExecutionLogs, but don't expose on the build endpoint.

  • Severity, timestamp and string
  • A new endpoint to grab the data (build/{id}/logs)
  • Info on the steps and then they occurred
  • Warn things link USFM errors, no prestranslations

Option 2 - serval log

Or we could create Engine logs - that keep growing for every step of the build and endpoint call. We could (A) shoehorn it into Loki or (B) make a new collection with the "last 200 messages" per engine.

Option 3 - just add more to EngineData

Or, we can add warning fields to ExecutionData such as
"Warning:type of warning": "here is a description of what happened"

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

No branches or pull requests

2 participants