When a scraper stops emitting an insight, the UI does not explain why the insight remains open or when it will resolve. For example, a GitHub Dependabot alert can be fixed in GitHub and disappear from the latest scrape result, while the catalog insight remains open until retention.staleAnalysisAge elapses. With the default 48h retention window, this looks like the scraper failed to resolve the alert even though it is actually waiting on stale retention.
The insight view should show a clear message such as: "This was not seen in the last X scrape runs. If this keeps happening, this alert will resolve at TIMESTAMP due to stale retention of Xh."
We should also consider a manual resolve action for cases where the source system has already resolved the issue and waiting for retention creates confusion.
When a scraper stops emitting an insight, the UI does not explain why the insight remains open or when it will resolve. For example, a GitHub Dependabot alert can be fixed in GitHub and disappear from the latest scrape result, while the catalog insight remains open until
retention.staleAnalysisAgeelapses. With the default 48h retention window, this looks like the scraper failed to resolve the alert even though it is actually waiting on stale retention.The insight view should show a clear message such as: "This was not seen in the last X scrape runs. If this keeps happening, this alert will resolve at TIMESTAMP due to stale retention of Xh."
We should also consider a manual resolve action for cases where the source system has already resolved the issue and waiting for retention creates confusion.