[ZBX-16262] Zabbix monitor log file not work Created: 2019 Jun 14  Updated: 2019 Jun 14  Resolved: 2019 Jun 14

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Agent (G)
Affects Version/s: 3.0.27
Fix Version/s: None

Type: Problem report Priority: Major
Reporter: joechan Assignee: Edgar Akhmetshin
Resolution: Won't fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

RHEL 7.6
Docker CE 18.09.3
Kubernetes 1.13.3

Attachments: PNG File host.PNG     PNG File items.PNG     PNG File items_deatil.PNG     PNG File k8s_deployment.PNG     PNG File trigger.PNG     PNG File trigger_detail.PNG    

 Description   

Steps to reproduce:

  1. The Zabbix is deployed in Kubernetes with monitoringartist/dockbix-xxl images
  2. The corresponding server and web port is expose as certain NodePort through k8s services
  3. The Zabbix agent is installed in other server (non docker container)
  4. We would like to monitor the log of that server which is installed Zabbix agent
  5. The log monitoring function is not trigger even if the string is matched in the log's content

Result:
No trigger in problem section under Zabbix web console
Expected:
To trigger the alert under Zabbix web console

 Comments   
Comment by Edgar Akhmetshin [ 2019 Jun 14 ]

Hello Joechan,

Thank you for reporting the issue. For this type of checks to work, it is necessary that active checks work. To do this, check the availability of port 10051 from your cluster from Agent host, the presence of processes like trapper and the variables used for Hostname=centos7 on agent configuration file and Zabbix web frontend. In addition, it is necessary to verify that you are receiving data for this element - see Monitoring - > Latest data - > centos7 - > Alertingtest.

Also please note, STR trigger function is case-sensitive and you have specified second argument to 1 second, do you have actual incoming data for such logical expression?

Please be advised that this section of the tracker is for bug reports only. The case you have submitted can not be qualified as one, so please reach out to [email protected] for commercial support or consultancy services. Alternatively, you can also use our IRC channel or community forum (https://www.zabbix.com/forum) for assistance. With that said, we are closing this ticket. Thank you for understanding.

Regards,
Edgar

Generated at Thu Apr 25 05:18:53 EEST 2024 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.