Make the detector_config_log freshness check less sensitive #436
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
Per discussion with @ian-r-rose , loosen the monitor threshold on the Station config's freshness since it may occasionally lag behind more than 3 days.
fix bug
fix bug
This adjustment seems reasonable based on the frequency that districts update the equipment set files and now that the district 8 automated update for the equipment set file is not being done daily. |
ian-r-rose
approved these changes
Oct 31, 2024
|
@pingpingxiu-DOT-ca-gov just wanted to make sure you saw my question above |
|
Per our discussion, station/controller changing frequencies are very different on detectors. |
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.
Adjusted the freshness warning to 14 days