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

Aggregate ONI Agent logs into NCA #348

Open
jechols opened this issue Oct 28, 2024 · 0 comments
Open

Aggregate ONI Agent logs into NCA #348

jechols opened this issue Oct 28, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jechols
Copy link
Member

jechols commented Oct 28, 2024

It's annoying to have to switch systems in order to figure out what happened on a given ONI Agent job. NCA should capture this stuff, at least in cases of an error.

This kind of depends where we go with #347 : if we end up with a single job that both runs and waits for the agent, we attach logs to that new job. If we don't, we really want to attach logs to the "run" job, not the "wait" job, but that's not really doable since logs aren't available when the "run" job is done.

Maybe this is a vote for merging the two and figuring out how to make that work....

Also, if we update the agent to parse logs and return more specific information, we may be able to do away with this ticket entirely. A clearer response from the agent means we don't need the low-level logs (and ONI's logs are often not super helpful). So this is blocked by #347 for the moment.

@jechols jechols added the enhancement New feature or request label Oct 28, 2024
@jechols jechols added this to Scoop Oct 28, 2024
@jechols jechols moved this from To do to In progress in Scoop Jan 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: In progress
Development

No branches or pull requests

1 participant