[ZBX-16036] Items using discard unchanged preprocessing do not reset failed status Created: 2019 Apr 23 Updated: 2019 May 03 Resolved: 2019 May 01 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Proxy (P), Server (S) |
Affects Version/s: | 4.2.1 |
Fix Version/s: | 4.2.2rc1, 4.4.0alpha1, 4.4 (plan) |
Type: | Problem report | Priority: | Major |
Reporter: | Malcolm | Assignee: | Vladislavs Sokurenko |
Resolution: | Fixed | Votes: | 0 |
Labels: | preprocessing | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Attachments: | 01-Configure Item.png 02-Configure Preprocessing, discard.png 03-Capture Data.png 04-Failure.png 05-Recovers from failure after removing preprocessing, discard.png |
Team: | Team A |
Sprint: | Sprint 51 (Apr 2019) |
Story Points: | 0.5 |
Description |
Steps to reproduce:
Expected:
|
Comments |
Comment by Arturs Lontons [ 2019 Apr 23 ] |
Hi, Thank you for reporting the issue. I think this actually calls for further discussion. Either such a behavior should be documented and a use of the heartbeat functionality should be recommended as a solution, or this should be treated as a bug. Reassigning this to the development team. |
Comment by Vladislavs Sokurenko [ 2019 Apr 29 ] |
Thank you for your report, issue reproduced, this is happening when value is already unsupported before it reaches preprocessing, for example invalid username or password with vmware.version key, in this case previous value is not deleted so when new valid value comes again and it is the same, then it's throttled and item remains unsupported. Previous value must be deleted when item becomes unsupported so that when new supported value comes it would not be throttled. |
Comment by Vladislavs Sokurenko [ 2019 Apr 30 ] |
Fixed in development branch: |
Comment by Vladislavs Sokurenko [ 2019 Apr 30 ] |
Fixed in:
|