Project

General

Profile

Actions
Copy link

action #112946

closed

coordination #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

Added by okurz almost 2 years ago. Updated 11 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
mkittler
Category:
Feature requests
Target version:
Ready
Start date:
2022-06-23
Due date:
% Done:

0%

Estimated time:

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

Related issues 1 (1 open — 0 closed)

Copied to openQA Project - action #112949: Exercise to switch off non-critical features and conduct emergency drillsNew2022-06-23

Actions
Actions
Copy link

Also available in: Atom PDF