Conversation
Contributor
|
For anomaly situations lately this has been obsid=0 or -1. Should those be special cased and the rest still be warnings? |
Member
Author
|
That's only for anomalies that reset the OBC. If we have a BSH we'll still have this situation showing a processing error every day for a month. |
jeanconn
approved these changes
Dec 8, 2022
This was referenced Jan 4, 2023
Merged
Merged
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
2 participants
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.
Description
This removes the word
WARNINGfrom the logging text for a situation that is common in anomaly recovery scenarios. This will reduce unnecessary alerts in Ska job watch.Interface impacts
None
Testing
No testing given the scope of the change.