Selecting a custom schema when adding KPIs

[mvaerle]

Tell us about the problem you're trying to solve

For postgres, there is data in custom schemas which is not being read. We cannot add KPIs directly using those tables via the TABLE functionality. In our case information from different sources lives in different schemas in the data warehouse.

Describe the solution you'd like

The process of adding a KPI would become easier if we can read data in custom schemas as well using the TABLE functionality. A drop-down to select the schema from which we need to read the data might solve this.

Describe alternatives you've considered

Use the QUERY functionality to write a custom query for defining the KPIs in order to use data outside public schema.

Additional context

In postgres, a DB can have many schemas and each schema has tables - Databases -> Schemas -> Tables. The default schema is named public. Currently, only the tables under the default public schema are being read for direct use.

[github-actions]

Hello there, thanks for opening your first issue. We welcome you to the community!

[manassolanki]

Scheme availability in different DB/DW which Chaos Genius provide as the data source.

• Postgres: Schema exist
• MySQL: Schema exist
• Google BigQuery: Schema doesn't exist
• Snowflake: Schema exist
• Redshift: Schema exist
• Third-Party Connector: Same as the Postgres (schema exist)

The KPI creation form needs to handle the schema selection on basis of the data source selected.

[manassolanki]

Fixed the issues via #502. This will be released in the v0.3.0