Spaces:
Running
Running
| # ThoughtSpot Quality Reporting Source | |
| The DemoPrep quality reporting liveboard is: | |
| - URL: `https://se-thoughtspot-cloud.thoughtspot.cloud/#/pinboard/85ccf9c9-2487-40b6-9f97-f9cf5207436b` | |
| - Liveboard name: `demoprep testing` | |
| - ThoughtSpot model: `demoprep_test_data` | |
| - Model GUID: `db310fd7-b382-49d2-8398-b2f378d179f6` | |
| - Physical table: Postgres `public.ts_quality_results` | |
| - ThoughtSpot table GUID: `c12ee8a3-2b5d-4597-a873-eddb9ffaddc5` | |
| Important: this reporting liveboard does **not** read from `session_logs`. | |
| `session_logs` is useful for pipeline-stage diagnostics and run lineage, but deleting | |
| bad rows from `session_logs` will not remove them from the quality reporting charts. | |
| The liveboard's score charts use `ts_quality_results`, including: | |
| - `Weekly Average Score Trend`: `average [Total Score] [Run Timestamp].weekly` | |
| - `Weekly Average Data Score Trend`: `average [Data Score] [Run Timestamp].weekly` | |
| - `Daily Data Score Trend`: `average [Data Score] [Run Timestamp].daily [Run Timestamp] = 'last 3 weeks'` | |
| Cleanup workflow: | |
| 1. Inspect the liveboard TML if the source is uncertain. | |
| 2. Query `ts_quality_results` for the affected date window. | |
| 3. Delete or filter rows in `ts_quality_results`, not only `session_logs`, when the | |
| reporting liveboard needs to change. | |
| 4. Use `session_logs` only to validate run provenance, user, stage completion, and | |
| failure causes. | |