Ad Widget

Collapse

help with log file monitor item

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • dle
    Junior Member
    • Feb 2008
    • 9

    #1

    help with log file monitor item

    hello,

    I have been trying to get log file monitoring to work for over a week now.

    I have searched the forums as much as I could and read the online manual.


    Here is what I have setup for the item:

    type: zabbix agent(active)

    key: log["/usr/local/jboss/server/default/log/server.log", "OutOfMemoryError","UTF-8", 1000]

    Type of Information: Log


    Latest data shows "Accessible only as an active check"

    Checked the zabbix agent log file:
    28076:20100922:082210.287 zabbix_agentd active check started [zabbix:10051]
    I do not see any errors in the zabbix agent log.

    I have confirmed in the zabbix_agentd.conf Hostname is exactly the same as the frontend GUI(including case sensitivity).

    Disableactive is commented out.

    Only one zabbix server and able to collect other data with zabbix agent ie. cpu stats and zabbix-sender items.

    Running zabbix server: 1.8.3 and zabbix agent 1.8.3.

    Please let me know what I have missed.

    Thank you
    Dat
    Last edited by dle; 22-09-2010, 18:04.
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #2
    start simple. try to monitor some small logfile with specifying logfile path only.
    make sure zabbix user has read access to that file.

    currently you have too many factors that could break it, so try to isolate possible factors before wasting too much time on it - for example, check whether monitoring cpu load as an active item works
    Zabbix 3.0 Network Monitoring book

    Comment

    • dle
      Junior Member
      • Feb 2008
      • 9

      #3
      Thank you richlv for your suggestion on troubleshooting!!!

      After setting the key to just monitor the log file. It worked fine.

      I added the text to match on and still worked fine.

      After deducing which option broke the monitoring. It was the "UTF-8", when I didn't define the encoding, worked perfectly!!!!


      Thank you very much!
      Dat

      Comment

      Working...