[ZBXNEXT-8330] Default values in Zabbix agent 2 plugin items with Session support Created: 2023 Mar 07 Updated: 2024 Apr 10 Resolved: 2023 Jun 20 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Agent2 plugin (G) |
Affects Version/s: | None |
Fix Version/s: | 5.0.35rc1, 6.0.18rc1, 6.4.3rc1, 7.0.0alpha1, 7.0 (plan) |
Type: | Change Request | Priority: | Trivial |
Reporter: | Eriks Sneiders | Assignee: | Eriks Sneiders |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||
Team: | |||||||||
Sprint: | Sprint 98 (Mar 2023), Sprint 99 (Apr 2023), Sprint 100 (May 2023), Sprint 101 (Jun 2023) | ||||||||
Story Points: | 2 |
Description |
To add Session defaults. For example special key-word When a session with this key-word is provided those connection parameters are used for every key in this plugin, but overwritten by parameters provided in the key or in the session provided by the key. Note! Originally it was discussed that it will affect every key. Which means even if you would submit and empty key, and have connection defaults provided in the configuration file, the key will use those defaults. Maybe it is better to use defaults only if session is provided? |
Comments |
Comment by Eriks Sneiders [ 2023 May 19 ] |
Implemented in
|
Comment by Marina Generalova [ 2023 Jun 13 ] |
Documentation updated:
Additionally, PostgreSQL plugin parameter page has been created and updated under a separate task. |