Skip to content

Decide fate of NSSP secondary signals #2099

@melange396

Description

@melange396

New signals were added to NSSP in issue #2073 / PR #2074 in the hope of getting more frequent updates, but that new source data has not been appended to or revised since Oct 18, 2024 (currently ~100 days out of date).

PR #2089 should cause Sir Complains-a-Lot to ignore those stale signals, thus preventing alerting on their age, and in turn allow us to get better alerting on the age of the "main" NSSP signals.

We need to decide on whether we should continue to attempt to collect these signals, and even if we should permanently retain any of that data in the DB. We essentially have only one real "issue" of those 4 signals, because we started acquiring them Dec 16, 2024 (after the latest revision of the source data) -- however, we continue to import the same data every week and tag it with a new "issue" date.

Some more discussion is available in a slack thread: https://delphi-org.slack.com/archives/C01LZ3A2UMU/p1736451710690869?thread_ts=1736404465.936839&cid=C01LZ3A2UMU

Metadata

Metadata

Assignees

Labels

API changeRenames, large changes to calculations, large changes to affected regionsdata qualityMissing data, weird data, broken data

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions