Adds lifecycle logger to log start, complete, and failure logs#1745
Merged
Conversation
…d-log-utils format for grafana alloy to pick up
alexpiet
approved these changes
May 27, 2026
arielleleon
approved these changes
May 27, 2026
Collaborator
arielleleon
left a comment
There was a problem hiding this comment.
Nice! It's great to see the log-schema dependency added
arjunsridhar12345
approved these changes
May 27, 2026
Collaborator
Author
|
okay I will merge and work with @jessy-liao to set up grafana alloy to rigs! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Describe changes:
Adds lifecycle logger to log start, complete, and failure logs using the aind-log-utils formatter. This will create a log file in a default folder of Documents/lifecycle_logs to be picked up by grafana alloy. Start log will emit after user presses start and acquisition name is defined and stop log will happen after user saves. Final logs will look like
What issues or discussions does this update address?
Describe the expected change in behavior from the perspective of the experimenter
Describe any manual update steps for task computers
Was this update tested in 446/447?
Does this update impact downstream processing by adding new saved files, or changing their format? If so, have you documented changes?