[ZBXNEXT-1866] Zabbix agent re-reads the log file from the first after changing the item key, log[], logrt[] and eventlog[] Created: 2013 Aug 20 Updated: 2013 Aug 23 Resolved: 2013 Aug 22 |
|
| Status: | Closed |
| Project: | ZABBIX FEATURE REQUESTS |
| Component/s: | Agent (G) |
| Affects Version/s: | 1.8.17 |
| Fix Version/s: | None |
| Type: | New Feature Request | Priority: | Trivial |
| Reporter: | MATSUDA Daiki | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
zabbix-1.8.16-not_update_lastlogsize_on_zabbix_active.patch
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Zabbix agent re-reads the log file from the first after changing the item key, log[], logrt[] and eventlog[]. Because when they are saved, the lastlogsize variable is updated to 0. So, Zabbix agent does so. I attached the patch. It adds the check botton to the WEB frontend to select update lastlogsize or not on Zabbix Active type. |
| Comments |
| Comment by richlv [ 2013 Aug 20 ] |
|
that's a known behaviour and setting mode flag to "skip" makes it process new records only in such case - only from 2.0, though. i don't think this should be changed for 1.8 at this time. |
| Comment by Oleksii Zagorskyi [ 2013 Aug 22 ] |
|
It duplicates a comment in |
| Comment by MATSUDA Daiki [ 2013 Aug 23 ] |
|
Thank you for your comments. I know the parameter in Zabbix-2.0.x. But I think that Zabbix-1.8.x is important. |