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

ui: aggregate error/warning table and corresponding admin UI #2724

Closed
spencerkimball opened this issue Sep 29, 2015 · 4 comments
Closed

ui: aggregate error/warning table and corresponding admin UI #2724

spencerkimball opened this issue Sep 29, 2015 · 4 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Milestone
1.0

Comments

@spencerkimball
Copy link
Member

Have logger store error and warning level log messages to a system table.
Provide a corresponding admin UI for viewing aggregate system warning+ log messages.
@spencerkimball spencerkimball self-assigned this Sep 29, 2015
@jess-edwards jess-edwards mentioned this issue Sep 29, 2015
Closed
78 tasks
@petermattis petermattis changed the title Aggregate error/warning table and corresponding admin UI ui: aggregate error/warning table and corresponding admin UI Feb 12, 2016
@petermattis petermattis added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Feb 14, 2016
@petermattis petermattis modified the milestone: Beta Feb 14, 2016
@petermattis
Copy link
Collaborator

I'm not sure if our log.{Warning,Error} messages have had enough consideration to be displayed as-is in the admin UI. Now that we have the event-log facility, I think we should make a pass over the log.{Warning,Error} occurrences and consider upgrading some of them to events.

@petermattis
Copy link
Collaborator

Punting this until after beta.

@petermattis petermattis modified the milestones: 1.0, Beta Mar 16, 2016
@maxlang
Copy link
Contributor

maxlang commented Apr 21, 2016

@mrtracy I'm going to assign to you as this seems related to #3725

@maxlang maxlang assigned mrtracy and unassigned spencerkimball Apr 21, 2016
@spencerkimball
Copy link
Member Author

@mrtracy seems we can close this. I don't believe this is necessary as it hasn't proven to be a pressing ask since it was filed 1.5 years ago. Re-open if you disagree.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
4 participants
@maxlang @spencerkimball @petermattis @mrtracy