Google-Symptoms suppress s05 low export errors #1805
Merged
Conversation
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
|
Ran the indicator locally today and compared with elastalert's slack message. 57 checks failed on the production run earlier today, and 57 checks were suppressed with the new parameters. |
neul3
approved these changes
Mar 14, 2023
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.
Description
The google-symptoms indicator has been exporting minimal data for the s05 signals, which is causing validation failures and blocking acquisition. Specifically, the s05_raw and s05_smoothed signals for the MSA, HRR, and county geo levels are causing the validation failures. They are receiving critical errors for the check_missing_geo_sig_date_combo, empty_reference_data and check_min_max_date validation checks.
Params files and templates have been updated for google symptoms to suppress errors for these geo-signal pairs. The indicator should now run even with no export from these particular geo-signal pairs.
Changelog
Add geo-signal pairs to the suppressed errors section
Fixes