[ZBXNEXT-5037] Skip paramerter for vmware.eventlog key Created: 2019 Feb 14 Updated: 2024 Apr 10 Resolved: 2019 Mar 05 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | None |
Fix Version/s: | 4.0.6rc1, 4.2.0beta2, 4.2 (plan) |
Type: | Change Request | Priority: | Minor |
Reporter: | Elina Kuzyutkina (Inactive) | Assignee: | Michael Veksler |
Resolution: | Fixed | Votes: | 3 |
Labels: | logmonitoring, vmware | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||||||||||||||||||
Team: | Team A | ||||||||||||||||||||
Sprint: | Sprint 49 (Feb 2019), Sprint 50 (Mar 2019) | ||||||||||||||||||||
Story Points: | 1 |
Description |
Currently there is no analog parameter for "skip" for the key vmware.eventlog. In situations where the log contains several years of events, with small polling intervals Zabbix does not have time to receive and process the entire accumulated history of events. A possible workaround is to change the parameter lastlogzise for the item directly in the database (but to do it safetly it's needed to stop Zabbix server to run update query) Most often it is unacceptable way. |
Comments |
Comment by Glebs Ivanovskis [ 2019 Feb 18 ] |
Related to/Caused by |
Comment by Michael Veksler [ 2019 Feb 27 ] |
Available in:
|
Comment by Glebs Ivanovskis [ 2019 Feb 27 ] |
This can comfortably fit in one line:
zabbix_log(LOG_LEVEL_TRACE, "createdTime is missing for event key '" ZBX_FS_UI64 "'",
key);
MVekslers Done. |
Comment by Michael Veksler [ 2019 Feb 28 ] |
Template available in:
|