BigQuery Tables

Organized by Project ID. Links are in the form project_id.dataset_id.table_id.

sheriff-o-matic[-staging]

sheriff-o-matic-staging.events.alerts: contains alerts generated by sheriff-o-matic-staging analyzer cron jobs. Proto: som.events.SOMAlertsEvent
sheriff-o-matic-staging.events.annotations: contains one row for each user-generated annotation event on sheriff-o-matic-staging. These include alert actions like snoozing, grouping or commenting. Proto: som.events.SOMAnnotationEvent
sheriff-o-matic.events.alerts: contains alerts generated by sheriff-o-matic analyzer cron jobs. Proto: som.events.SOMAlertsEvent
sheriff-o-matic.events.annotations: contains one row for each user-generated annotation event. These include alert actions like snoozing, grouping or commenting. Proto: som.events.SOMAnnotationEvent

test-results-hrd.events.test_results: contains one row for each test run collected by the test-results server. Includes test names, expected/actual results, chromium revision etc. Proto: testresults.event.TestResultEvent
test-results-test-hrd.events.test_results: contains one row for each test run collected by the test-results staging server. Includes test names, expected/actual results, chromium revision etc. Proto: testresults.event.TestResultEvent

All Tricium server instances have:

analyzer.results: contains results for each run (i.e. each AnalyzeRequest). Proto: AnalysisRun
events.feedback: contains rows for commenting and “not useful” reporting events. Proto: FeedbackEvent

The project “commit-queue” has these tables for CQ data: