MAAS should assess PostGRES configuration
Bug #1702649 reported by
Mark Shuttleworth
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Invalid
|
Wishlist
|
Unassigned | ||
Bug Description
The postgres settings behind a MAAS are material for performance. As part of the overall service monitoring framework, I would include PostGRES and show traffic lights (green, amber, red) related to postgres availability and suitability of configuration. We might also monitor memory pressure on the postgres hosts as a way of helping people right-size the backend of their MAAS deployment.
| tags: | added: performance |
| Changed in maas: | |
| milestone: | none → 2.3.0 |
| importance: | Undecided → Critical |
| importance: | Critical → High |
| importance: | High → Wishlist |
| status: | New → Triaged |
| Changed in maas: | |
| milestone: | 2.3.0 → 2.3.x |
Revision history for this message
| Jerzy Husakowski (jhusakowski) wrote | #1 |
| Changed in maas: | |
| milestone: | 2.3.x → none |
| status: | Triaged → Invalid |
To post a comment you must log in.
There are now Ansible playbooks that help deploy MAAS and Postgres in recommended configuration, and in this cycle they are being extended with observability setup. This will provide an initial set of parameters to observe and draw conclusions about performance and suitability of configuration via the observability stack. Marking as invalid as it's a feature request that is already on the roadmap, currently in execution.