[ZBXNEXT-4089] Move ODBC DSN to a separate field and allow free format keys for database monitor items Created: 2017 Sep 06  Updated: 2018 Jan 24

Status: Open
Project: ZABBIX FEATURE REQUESTS
Component/s: Frontend (F), Server (S)
Affects Version/s: 4.0.0alpha1
Fix Version/s: None

Type: New Feature Request Priority: Minor
Reporter: Glebs Ivanovskis (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: odbc, usability
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Sub-task
depends on ZBXNEXT-4086 Extend item preprocessing with functi... Closed

 Description   

Currently db.odbc.select and db.odbc.discovery have two mandatory parameters. One of them is data source name (DSN) and another one is just ignored when performing check:

The unique description will serve to identify the item in triggers etc.

It makes sense to store DSN in a separate dedicated field along with username and password. If db.odbc.discovery is obsoleted by ZBXNEXT-4086 we will only have one ODBC key possible and we can allow users to have meaningful keys without db.odbc.select prefix.


Generated at Fri Mar 29 16:18:44 EET 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.