[ZBXNEXT-7436] Add mysql.custom.query key to Zabbix Agent and Zabbix Agent 2 Created: 2022 Jan 20  Updated: 2024 Apr 10  Resolved: 2023 Nov 08

Status: Closed
Project: ZABBIX FEATURE REQUESTS
Component/s: Agent (G), Agent2 plugin (G)
Affects Version/s: None
Fix Version/s: 6.0.21rc1, 6.4.6rc1, 7.0.0alpha4, 7.0 (plan)

Type: New Feature Request Priority: Trivial
Reporter: Aleksey Volodin Assignee: Eriks Sneiders
Resolution: Fixed Votes: 12
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
Duplicate
is duplicated by ZBXNEXT-8144 allow mysql custom query Closed
Sub-Tasks:
Key
Summary
Type
Status
Assignee
ZBXNEXT-8598 Add mysql.custom.query key for to Zab... Specification change (Sub-task) Closed Andrejs Kozlovs  
Team: Team INT
Sprint: Sprint 102 (Jul 2023), Sprint 103 (Aug 2023), Sprint 104 (Sep 2023), Sprint 105 (Oct 2023), Sprint 106 (Nov 2023)
Story Points: 1.5

 Description   

For now we have a nice template for Zabbix Agent 2 and sets of UserParameter for Zabbix agent.

This two solution cover normal monitoring for MySQL. But in some situation customer want to execute some custom query. In fact custom query present in PostgreSQL monitoring trough Zabbix Agent 2.



 Comments   
Comment by Nathan Liefting [ 2022 Apr 26 ]

Massive +1 😁 Really thought we had this already, surprised to find it isn't present for MySQL yet even though Postgres and Oracle support it already.

Comment by Oliver Czempas [ 2023 Apr 25 ]

Is there a roadmap, when it comes? Would be very important to me

Comment by Leonardo Savoini [ 2023 Jul 19 ]

I need it too.

And also, this is one of the queries I need show engine ndbcluster status;

Comment by Thiago Melo [ 2023 Jul 25 ]

Hi, why it was closed as "Unresolved'?

Comment by Eriks Sneiders [ 2023 Jul 25 ]

Hi, thiago.melo

There might be some confusion, a duplicate ticket ZBXNEXT-8144 is closed, this ticket is currently open and awaiting review and quality assurance. I hope this helps clear up the confusion.

Comment by Thiago Melo [ 2023 Jul 25 ]

Ahh, ok, it is because, in this ticket I can see "Status: Resolved, Resolution: Unresolved"

Comment by Eriks Sneiders [ 2023 Aug 10 ]

Implemented in:

Comment by Lidija Marsova (Inactive) [ 2023 Aug 14 ]

Documentation updated:

Generated at Sat Oct 04 22:11:58 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.