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.

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

Create diagnostic table of each component's data gathering #14

Open
jessehamner opened this issue Jan 1, 2021 · 0 comments
Open

Create diagnostic table of each component's data gathering #14

jessehamner opened this issue Jan 1, 2021 · 0 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jessehamner
Copy link
Owner

Proposed: a "status table" or "dashboard" composed of an aggregated JSON file that contains go/no-go and, where practical, at least a category of failure, for each subcomponent of the project. Thus, if the forecast map fails but everything else is obtained okay, the table would be mostly "green", with perhaps an indicator marker of "yellow", indicating the user might want to see what has gone wrong.
Individual subsystems could put their diagnostic data into the standard JSON output, that could then be collected by a new class, and served up as a discrete JSON API endpoint using Flask, as most of the data is already served up that way.

@jessehamner jessehamner added enhancement New feature or request documentation Improvements or additions to documentation labels Jan 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant