[ UI ] QAN for Postgresql attempts to connect to a database with the same name as the username
General
Escalation
General
Escalation
Description
How to test
None
How to document
None
Attachments
6
is cloned by
relates to
Smart Checklist
Activity
Show:
Done
Details
Details
Assignee
Unassigned
UnassignedReporter

Priority
Components
Needs QA
Yes
Fix versions
Story Points
1
Sprint
None
Smart Checklist
Open Smart Checklist
Smart Checklist

Open Smart Checklist
Created December 9, 2020 at 12:50 PM
Updated November 13, 2024 at 8:43 AM
Resolved March 8, 2021 at 11:56 AM
Impact on the user:
User is unable to see Table and indexes data/information for PG monitoring
Steps to reproduce:
Verified with PMM 2.13.0 and
Install PMM-server
configure PG and create a user as described in the document
https://www.percona.com/doc/percona-monitoring-and-management/2.x/setting-up/client/postgresql.html
Add Postgresql to pmm monitoring: (Username is pmm_user )
PG commands:
Actual result:
PMM QAN:
PG Queries (INSERT) has the following in Tables and Examples:
pq: database "pmm_user" does not exist
Expected Result:
PMM uses the correct database and information about Tables and indexes exists
Workaround:
N/A
Details
Original report:
When using QAN with postgres, click on "tables" tab shows the same error:
Maybe it should connect to the default "postgres" or the public schema instead of attempting
Suggested implementation:
1. Database name is presented on rows on endpoint /GetReport.
2. If database property is presented and not empty use it for "v1/management/Actions/StartPostgreSQLShowCreateTable".
See screenshot:
We already sending db name in "v0/qan/ObjectDetails/GetMetrics"