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

Notify users when probes are not meeting their deadlines #1379

Open
2opremio opened this issue Apr 25, 2016 · 3 comments
Open

Notify users when probes are not meeting their deadlines #1379

2opremio opened this issue Apr 25, 2016 · 3 comments
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality help-wanted An issue that would be good for non-maintainers to attempt

Comments

@2opremio
Copy link
Contributor

2opremio commented Apr 25, 2016 •
edited
Loading

See #897 (comment)
@2opremio 2opremio added the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label Apr 25, 2016
@2opremio 2opremio added this to the 0.15.0 milestone Apr 25, 2016
This was referenced Apr 25, 2016
Closed
Closed
@tomwilkie tomwilkie removed this from the 0.15.0 milestone Apr 29, 2016
@2opremio
Copy link
Contributor Author

We should probably also provide feedback when probes are intentionally dropping reports, but that's trickier.

@tomwilkie
Copy link
Contributor

Dupe of #551? In that ticket we suggest that we keep the latest report from every probe we have ever seen, and if the report is older than the collection window we display the nodes from that report as greyed out (to indicated failed).

@2opremio 2opremio mentioned this issue May 23, 2016
Merged
@2opremio
Copy link
Contributor Author

2opremio commented Jun 17, 2016 •
edited
Loading

Related #943

@rade rade added the chore Related to fix/refinement/improvement of end user or new/existing developer functionality label Jul 4, 2016
@davkal davkal added the help-wanted An issue that would be good for non-maintainers to attempt label Oct 14, 2016
@rade rade removed the component/ui Predominantly a front-end issue; most/all of the work can be completed by a f/e developer label Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore Related to fix/refinement/improvement of end user or new/existing developer functionality help-wanted An issue that would be good for non-maintainers to attempt
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@rade @tomwilkie @davkal @2opremio