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.

Sign up for GitHub

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

Jump to bottom

Downtime detection #3

Closed
geertw opened this issue Apr 6, 2019 · 0 comments
Closed

Downtime detection #3

geertw opened this issue Apr 6, 2019 · 0 comments
Labels
feature New feature or request

Comments

@geertw
Copy link
Member

geertw commented Apr 6, 2019

Implement downtime detection, particularly for departures and arrivals.

A threshold must be defined. If the average number of messages during a 10 minute-window drops below the threshold, the component is considered to be DOWN. When the average number of messages increases above the threshold, the component is considered to be RECOVERING for a defined time (70 minutes for departures) before it is UP again.
@geertw geertw added the feature New feature or request label Apr 6, 2019
geertw added a commit that referenced this issue Apr 24, 2019
@geertw
Check message flow, detect downtime #3
eacd871
@geertw geertw closed this as completed Apr 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@geertw