Reporting Stack Production Readiness

This is a work in progress.  Goal is to capture stories/potential bugs that get the reporting stack to a place that's more ready to be adopted by an implementer.  This is not a document with scope.

Current Epic

OLMIS-6046 - Getting issue details... STATUS

Upgrading

As an implementer I want the OpenLMIS packaged reports to be updated automatically when I upgrade OpenLMIS so that I may stay up to date with the community.

As an implementer I want my custom reports to be unaffected when I update OpenLMIS so that my custom reports stay as I built them.

Development Documentation

As a implementer I want to have an ERD automatically generated of the reporting database so that I may evaluate the structure and plan my reporting efforts efficiently.

As an implementer I want to have guidance for how to add my own report pipeline (Nifi, Nifi Registry, Postgres and Superset) so that I can have my custom reports alongside the shipped reports

Monitoring & Alerting

As an implementer I want to be able to see how long data is moving through the system, and where the bottlenecks are, so that I know what sort of performance I'm achieving.

As an implementer I want to know when any portion of the data pipeline falls below my availability threshold so that I know when something becomes too slow or isn't useable.

Deployment

As an implementer I want to know how to deploy the reporting stack quickly so that I may setup staging and production environments

• This seems to be the best document atm:  Stand-up and Configure the Reporting Stack
• If I run what's in the README, and follow that guide, Nifi starts, but superset doesn't.

Security

Possible bug:  is this basic auth screen supposed to be showing?