[ZBX-15260] logrt[]: warning "there are no files matching "....." in "....."" can be misleading Created: 2018 Dec 04  Updated: 2024 Apr 10  Resolved: 2018 Dec 21

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 3.0.24, 4.0.2, 4.2.0alpha2
Fix Version/s: 3.0.25rc1, 4.0.4rc1, 4.2.0alpha2, 4.2 (plan)

Type: Problem report Priority: Trivial
Reporter: Andris Mednis Assignee: Andrejs Sitals (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Unix, MS Windows


Team: Team A
Sprint: Sprint 47, Dec 2018
Story Points: 0.125

 Description   

Steps to reproduce:

  1. Create logrt[] item, e.g. logrt[/home/zabbix/test.log]
  2. Append test record, e,g. echo ABC >> /home/zabbix/test.log
  3. Observe that test record is reported to server.
  4. Append a new test record to a new file, e.g. echo 123 >> /home/zabbix/test.log1
  5. Observe that test record is reported to server.
  6. Delete the new log file /home/zabbix/test.log1.
  7. In agent log file a warning is logged "there are no files matching "test.log" in "/home/zabbix/".

This is confusing for user because there is a log file test.log, which matches the regexp, it is just skipped as already processed.

Proposed solution: modify warning message to look like

there are no recently modified files matching "test.log" in "/home/zabbix/"



 Comments   
Comment by Andrejs Sitals (Inactive) [ 2018 Dec 20 ]

Available in versions:

  • pre-3.0.25rc1 r88013
  • pre-4.0.4rc1 r88014
  • pre-4.2.0alpha2 (trunk) r88016
Comment by richlv [ 2019 Jan 22 ]

(1) The current changelog entry:

improved misleading warning message when agent fails to find log file during processing logrt[] item

Might read better as one of:

  • improved a misleading warning message when agent fails to find a log file during the processing of a logrt[] item
  • improved a misleading warning message when agent fails to find a log file while processing a logrt[] item
Generated at Fri Apr 26 06:43:51 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.