QAN Not showing any data for the Service/DB

Percona Monitoring and Management (PMM) PMM 2.x
,
1

Description:

PMM QAN won’t show the service/db of a specific Postgres Target any further after a few hours of it working.

Tried performing a reboot of my ec2 instance which is running the pmm docker, didn’t help any…

pmm-agent.log shows:

level=warning msg=“Can’t extract table names from query NOT (SELECT ARRAY(SELECT json_object_keys(j)) @> keys): error on parsing sql query: syntax error at or near "NOT"” agentID=/agent_id/8b17f306-738b-43da-ade9-e99dd1d8a53b component=agent-builtin type=qan_postgresql_pgstatements_agent

time=“2024-11-19T15:33:00.053+00:00” level=warning msg=“Can’t extract table names from query
…values ($1, $2, $3), ($4, $5, $6), ($7, $8, $9), ($10, $11, $12), ($13, $14, $15), ($16, $17, $18), ($19, $20, $21), ($22, $23, $24), ($25, $26, $27), ($28, $29, $30), ($31, $32, $33), ($34, $35, $36), ($37, $38, $39), ($40, $41, $42), ($43, $44, $45), ($46, $47, $48), ($49, $50, $51), ($52, $53, $54), ($55, $56, $57), ($58, $59, $60), ($61, $62, $63), ($64, $65, $66), ($67, $68, $69), ($70, $71, $72), ($73, $74, $75), ($76, $77, $78), ($79, $80, $81), ($82, $83, $84), ($85, $86, $87), ($88, $89, $90), ($91, $92, $93), ($94, $95, $96), ($97, $98, $99), ($100, $101, $102), ($103, $104, $105), ($106, $107, $108), ($109, $110, $111), ($112, $113, $114), ($115, $116, $117), ($118, $119, $120), ($121, $122, $123), ($124, $125, $126), ($127, $128, $129), ($130, $131, $132), ($133, $134, $135), ($136, $137, $138), ($139, $140, $141), ($142, $143, $144), ($145, $146, $147), ($148, $149, $150), ($151, $152, $153), ($154, $155, $156), ($157, $158, $159), ($160, $161, $162), ($163, $164, $165), ($166, $167, $168), ($169, $170, $171), ($172, $173, $174), ($175, $176, $177), ($178, $179, $180), ($181, $182, $183), ($184, $185, $186), ($187, $188, $189), ($190, $191, $192), ($193, $194, $195), ($196, $197, $198), ($199, $200, $201), ($202, $203, $204), ($205, $206, $207), ($208, $209, $210), ($211, $212, $213), ($214, $215, $216), ($217, $218, $219), ($220, $221, $222), ($223, $224, $225), ($226, $227, $228), ($229, $230, $231), ($232, $233, $234), ($235, $236, $237), ($238, $239, $240), ($241, $242, $243), ($244, $245, $246), ($247, $248, $249), ($250, $251, $252), ($253, $254, $255), ($256, $257, $258), ($259, $260, $261), ($262, $263, $264), ($265, $266, $267), ($268, $269, $270), ($271, $272, $273), ($274, $275, $276), ($277, $278, $279), ($280, $281, $282), ($283, $284, $285), ($286, $287, $288), ($289, $290, $291), ($292, $293, $294), ($295, $296, $297), ($298, $299, $300), ($301, $302, $303), ($304, $305, $306), ($307, $308, $309), ($310 …: error on parsing sql query: syntax error at or near "…"” agentID=/agent_id/8b17f306-738b-43da-ade9-e99dd1d8a53b component=agent-builtin type=qan_postgresql_pgstatements_agent

Version:

ProjectName: pmm-managed
Version: 2.42.0
PMMVersion: 2.42.0
Timestamp: 2024-06-06 09:43:55 (UTC)
FullCommit: 74e57527735bd062c4bd37adbd89c31bb14ebc15

Logs:

[If applicable, include any relevant log files or error messages]

Expected Result:

QAN should show my Service/DB for approx 3 Hours, before it disappears from QAN entirely.

2

Bumping for Visibility.

Thank you!

3

Any insights is greatly appreciated!

Thank you!

4

Hello @Thomas_Baran
Thank you for the details.

It would be good to know pmm-client and Postgresql version as well so we can test this on our side.

Looking at the pmm-agent error log, it shows an issue with error on parsing sql query, which usually happens when versions are incompatible.

5

Thanks for responding!

pmm-client - I believe there’s no pmm-client installed since this is a supabase postgres instance which is similar to how RDS works - where you can’t ssh into the db server or install anything on it etc. They use K8’s i believe for their PG Pods which they offer as a service etc. To configure the PMM Service to connect to the PG instance - i used similar instructions which a RDS instance would require, except for the user I configured the PMM Service to use when logging into the DB is the equivalent of a superuser which Supabase exposes to its customers.

Postgresql Version: psql (16.3, server 15.1)

6

Hello @Thomas_Baran

Thank you for the details. As you mentioned, it’s a supabase PostgreSQL instance; this could be an issue with compatibility with the supabase postgres instance and PMM agent query parsing.

PMM is compatible and tested with PostgreSQL , Percona Distribution for PostgreSQL and Amazon RDS PostgreSQL instance

If you want you can raise issue as feature request here: https://perconadev.atlassian.net to support supabase PostgreSQL instance in PMM monitoring