Closed andreasohlund closed 11 years ago
Nice, I can work on this tomorrow
On Monday, September 2, 2013, Andreas Öhlund wrote:
VIP
Visualization:
-
Indicator should be green if no endpoints are failing
Indicator should be red if at least one endpoint is failing
Design:
Demo / Acceptance tests
Case 1:
- Run the videostore sample
- Heartbeat indicator should be green and the number 4 should be displayed
Case 2:
- Kill the sales endpoint
- Indicator should turn red within X seconds
- Number below inidcator should be 1
Case 3:
- Restart sales endpoint
- Indicator should turn green
Related to Epic GH link
— Reply to this email directly or view it on GitHubhttps://github.com/Particular/ServiceControl/issues/40 .
Regards John Simons NServiceBus
Comment regarding 1 minute timing:
I like the "active/inactive" => user can use that to mute endpoints that are known to be down and we can use that our self to turn the active on and off when we start to monitor endpoints starting/stopping for legitimate reasons
@dannycohen If you are ok with the current display for heartbeats, i.e. the text displays 'n' active endpoints, and a circle at the top indicates the number of failed endpoints, then this issue can be closed.
@andreasohlund - Since I am using a template that allows the button with the circle, I chose to display the number in a circle on the indicator itself as opposed to * Number of heartbeat failing endpoints should be displayed in red under the indicator icon (and next to the healthy heartbeats)
@indualagarsamy - current implementation is good. I'm missing the "location" aspect of the indicators / dashboard grid (i.e. which endpoints ? on which machines ? etc.) but that is something that is more relevant to #41 and #42
also i believe some of these user stories need to be in service pulse. The indicator being red or green is a service pulse concern, not service control. @dannycohen @andreasohlund @johnsimons - thoughts?
@indualagarsamy - Agreed. I'll close and move them to SP repo.
@andreasohlund - I believe ServiceControl has needed stuff for the heartbeat indicator. I am closing this issue. Feel free to reopen if you think we are still missing something in SC for the heartbeats feature.
As Opie, I want to be aware of endpoints that are not emitting heartbeats in a timely manner
Visualization:
Notes:
Demo / Acceptance tests:
Case 1:
Case 2:
Case 3:
Case 4: