Ad Widget

Collapse

Help with log[] item on windows host

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • veysl
    Junior Member
    • May 2014
    • 4

    #1

    Help with log[] item on windows host

    Hi!
    Please, help with log[] item on windows host.
    For log file monitoring on windows xp host I've create new template and new item with key
    log[c:\datalog\test.log,"ERR"]
    Type - Zabbix agent (active).
    type of information - Log
    Application - Zabbix agent.
    Version of Zabbix server 2.2.3
    Version of Zabbix client 2.2.1
    Now I see status for this item "not supported"
    On "latest data" I have not see new item in "zabbix agent" group .
    How can I set this item work properly?
    Should I add any sets in zabbix_agentd.win.conf file?
  • ingus.vilnis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Mar 2014
    • 908

    #2
    Hi!

    You can have a look at zabbix_agentd.win.conf file and check if you have set correct ServerActive= parameter. In your case it should be the same as Zabbix Server IP. Do not forget to restart Zabbix agent service on your Windows machine if you make any changes in config file.

    You can also try to remove quotation marks from your Item key. log[c:\datalog\test.log,ERR]

    If these steps do not help, we'll have to think of other solutions.

    Best Regards,
    Ingus

    Comment

    • veysl
      Junior Member
      • May 2014
      • 4

      #3
      It's start to work

      Hi! Big thanks for your answer.
      I have try change key string for many times with quote and without it and with reg expression and without and once upon a time it start to work.
      Working string is
      log["c:\datalog\test.log","ERR"]
      But there is one more issue. There is big lag between time of editing item and key and time when I can see new item value in dashboard and client log. Big lag happens ever after restarting zabbix client and zabbix server.
      Now I have found working string and can move forward. Thanks a lot for your advice!

      Comment

      • ingus.vilnis
        Senior Member
        Zabbix Certified Trainer
        Zabbix Certified SpecialistZabbix Certified Professional
        • Mar 2014
        • 908

        #4
        Hi!

        It is great that you finally got your log data coming in!

        Regarding delays in refreshing your data, they are affected by multiple parameters:
        • Update interval (in sec) in item setup
        • Administration -> General -> Other (from top right dropdown) -> Refresh unsupported items (in sec)
        • RefreshActiveChecks= parameter in zabbix_agentd.conf file


        What is your Update interval (in sec) for this item? For test try to set it to very few seconds. When you get the item working correctly you can increase the interval.

        Check Refresh unsupported items (in sec). This means that if your item goes Not supported, Zabbix will recheck it only after that given time, by default it was I think 600 seconds. Set it to somewhat less than that, for test like 10 seconds, but again don't forget to set it back on a production system.

        RefreshActiveChecks= parameter means how often Zabbix agent will reload active checks configurations. In other words, Zabbix agent needs to know what items should be checked and sent to server and whether the configuration has changed, and it is done every default 120 seconds.

        So this means that with default settings your log item with not supported status will start gathering data again after about 10+ minutes.

        Good luck configuring!

        Best Regards,
        Ingus

        Comment

        • veysl
          Junior Member
          • May 2014
          • 4

          #5
          This parameter work properly!

          Thanks a lot for your answer again. I have check it - change to 20 seconds and restart zabbix server and agent . Then I change item to wrong state and item status has changed to unsupported state in short time.
          Good luck for you, Ingus!

          Comment

          Working...