Actions
action #112946
closedcoordination #128366: [epic] further improvement after we did ensure all our database tables accomodate enough data
coordination #112961: [epic] Followup to "openqa.suse.de is not reachable anymore, response times > 30s, multiple alerts over the weekend"
Extend openQA documentation with best practices what to do after migration, e.g. look at pg_stats size:S
Description
Motivation¶
We learned during #112718 that it's a good idea to look at pg_stats if there are any "slow queries", either as regression from the migration or just from other issues and we have not realized yet. We should make sure our openQA database migration guide includes best practices as well.
Acceptance criteria¶
- AC1: Our documentation reminds what to do after migration
Suggestions¶
Updated by okurz almost 2 years ago
- Copied to action #112949: Exercise to switch off non-critical features and conduct emergency drills added
Updated by okurz almost 2 years ago
- Description updated (diff)
- Parent task changed from #112718 to #112961
Updated by mkittler 12 months ago
- Subject changed from Extend openQA documentation with best practices what to do after migration, e.g. look at pg_stats to Extend openQA documentation with best practices what to do after migration, e.g. look at pg_stats size:S
- Description updated (diff)
- Status changed from New to Workable
Actions