Predefined status/log entries #216
Closed
Conversation
This file contains 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.
Published as a draft for now for discussion and to build on.
I think there is a need to have a list of predefined system status logs/log entries. Already in UDMI, there are some are defined (for write back), but there's benefit in consolidating these into one file as a reference, and to add additional information such as log levels.
Additionally, we're now asking device manufacturers to send out some logs (e.g. a system start up log entry) but we are not defining the details of this.
Without doing so, different devices may represent the same issues/logs/status differently
This attempts to consolidate the log entries and define the minimum log entries needed