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

Already on GitHub? Sign in to your account

Track Screen State #157

Closed
bamnet opened this Issue Jul 18, 2012 · 5 comments

Comments

Projects
None yet
2 participants
Owner

bamnet commented Jul 18, 2012

We need a way to track if a screen is offline or online per #122.

@ghost ghost assigned bamnet Jul 18, 2012

Owner

bamnet commented Mar 1, 2013

Is the last IP information relevant for everyday clients or should we leave that reporting to the hardware plugin? Maybe we just need a heartbeat time here.

Owner

augustf commented Mar 10, 2013

We should also be logging an activity and sending an email when the screen state changes - if the owning group members want that.

Owner

augustf commented Mar 10, 2013

@bamnet My thought is to have 2 more columns on screens - last_seen_at and is_online - a timestamp and a boolean. last_seen_at would be updated when the screen hit the frontend setup action. We would then update is_online accordingly when a certain amount of time elapsed with the screen either being seen or not.

This would allow the frontend screen numbers to be reasonable and would allow email (only once per outage) and activity triggers to happen.

This depends on two things - screens checking in with some backend code (which they'd need to do to get template updates?) and some means of repeatedly checking the last_seen_at column and judging if an outage has occurred.

For that, we'll need some cron-esque thing. But given that we don't want to use straight cron (not portable) and doing this with delayed_job will be evil. How about Clockwork (https://github.com/tomykaira/clockwork)? It's yet another daemon, but seems more rational than the alternatives.

Owner

bamnet commented Mar 10, 2013

is_online doesn't provide any value that we couldn't get with a scope or
method. I wonder if we should track the last_updated at the position level
too / instead.

On Mar 10, 2013, at 9:30 AM, August notifications@github.com wrote:

@bamnet https://github.com/bamnet My thought is to have 2 more columns on
screens - last_seen_at and is_online - a timestamp and a boolean.
last_seen_at would be updated when the screen hit the frontend setup
action. We would then update is_online accordingly when a certain amount of
time elapsed with the screen either being seen or not.

This would allow the frontend screen numbers to be reasonable and would
allow email (only once per outage) and activity triggers to happen.

This depends on two things - screens checking in with some backend code
(which they'd need to do to get template updates?) and some means of
repeatedly checking the last_seen_at column and judging if an outage has
occurred.

For that, we'll need some cron-esque thing. But given that we don't want to
use straight cron (not portable) and doing this with delayed_job will be
evil. How about Clockwork (https://github.com/tomykaira/clockwork)? It's
yet another daemon, but seems more rational than the alternatives.


Reply to this email directly or view it on
GitHubhttps://github.com/concerto/concerto/issues/157#issuecomment-14684090
.

Owner

augustf commented Mar 10, 2013

Hmm-not sure if I see how a scope of method would provide the needed persistency to record screen status. But tracking the scope at the position level as well could provide some value.

@bamnet bamnet closed this in f40f37e Mar 12, 2013

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