Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chain should alert when we stop getting data #46

Open
ssfrr opened this issue Jan 9, 2015 · 1 comment
Open

Chain should alert when we stop getting data #46

ssfrr opened this issue Jan 9, 2015 · 1 comment

Comments

@ssfrr
Copy link
Member

ssfrr commented Jan 9, 2015

If we stop getting sensor data from a device that was previously giving data, we should send an alert email.

The logic would be to have a "failed" flag per-device. If we haven't heard from a device in a while we should set the "failed" flag. When a device becomes failed and wasn't failed before, we should send an alert.

We need to define the timespan after a device becomes failed that triggers an alert, maybe some multiple of the sampling rate (which we'd also need to add as a sensor property).

Anyways, this needs some discussion but would be a big help in knowing when things go down, so we're not scrambling later on because we didn't realize things were down.

@kkleidal
Copy link
Contributor

This could be incorporated with #29 . If we have the server writing to a stream when events are triggered, we could have a subscribed microservice which reads the stream of events and notices when events regarding certain devices stop coming (and then sends an email/SMS/tweet/etc). The microservice architecture would make the system more ready for change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants