You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
The text was updated successfully, but these errors were encountered:
Option 1 - build log
Add it to the Build repo structure add a field called ExecutionLogs, but don't expose on the build endpoint.
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"
The text was updated successfully, but these errors were encountered: