action #76903
Updated by okurz about 4 years ago
## User Story I would like us to be able to have some statistics about openQA test modules failures. How often each test modules fails, which fail the most often, what are the trends of failure rate.... ## Acceptance criteria * **AC1:** Current job module details from OSD are available on a SUSE instance of Metabase ## Out of scope Persistent database setup and configuration on osd with salt -> #78222 ## Suggestions * Use [the internal Metabase instance](https://maintenance-statistics.dyn.cloud.suse.de/) (login by OKTA credentials, but as login put only part of e-mail address before the @) * Look into exposing read-only database access to make queries available, e.g. similar to what we already do for "telegraf" in https://gitlab.suse.de/openqa/salt-states-openqa/-/blob/master/openqa/server.sls#L163 but including the "job_modules" table * take https://gitlab.suse.de/openqa/salt-states-openqa/-/merge_requests/395 as inspiration * Allow access to postgres database from outside "localhost": * Research security implications and "best practices", e.g. follow https://blog.bigbinary.com/2016/01/23/configure-postgresql-to-allow-remote-connection.html * Change postgres "listen" address in postgresql.conf to listen to the ethernet device and not only localhost, e.g. postgr * Change postgres config in pg_hba.conf to allow access for remote connections * Make sure that salt recipes ensure persistence of this configuration, maybe we should use https://github.com/saltstack-formulas/postgres-formula ?