-
-
Notifications
You must be signed in to change notification settings - Fork 287
Add notifications for collector failures #945
Copy link
Copy link
Open
Labels
contributor friendlyA well-scoped, approachable issue for someone looking to contribute.A well-scoped, approachable issue for someone looking to contribute.enhancementNew feature or requestNew feature or requestfrontendIssues that require updating non-typescript frontend code (e.g. css)Issues that require updating non-typescript frontend code (e.g. css)goIssues that require updating Go codeIssues that require updating Go codetypescriptIssues that require updating typescript codeIssues that require updating typescript code
Description
Metadata
Metadata
Assignees
Labels
contributor friendlyA well-scoped, approachable issue for someone looking to contribute.A well-scoped, approachable issue for someone looking to contribute.enhancementNew feature or requestNew feature or requestfrontendIssues that require updating non-typescript frontend code (e.g. css)Issues that require updating non-typescript frontend code (e.g. css)goIssues that require updating Go codeIssues that require updating Go codetypescriptIssues that require updating typescript codeIssues that require updating typescript code
We should add an API endpoint so the collector can report
smartctl --scanandsmartctl --infoerrors. The endpoint can trigger an opt-out notification. If the backend receives asmartctl --xalljson object indicating an error (see #944), a notification should also be sent.This needs a new handler, a new route:
scrutiny/webapp/backend/pkg/web/server.go
Lines 22 to 53 in 9d1ce79
and a new setting, including a UI element and database migration. See bdbe13e for an example.