Ad Widget

Collapse

Log files in windows - space in the name of the folder

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • richlv
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2005
    • 3112

    #16
    did you look at the zabbix manual for that item key ?
    Zabbix 3.0 Network Monitoring book

    Comment

    • zabbix_zen
      Senior Member
      • Jul 2009
      • 426

      #17
      Hmm.. I've bumped into exactly the same situation with an UCS-2 encoded file.

      Per log[file,<pattern>,<encoding>,<max lines>]
      I've tried configuring the item key encoding option both as "UCS-2" and "UTF-16" considering they come referenced the same in Wikipedia character encoding page

      [....,"INFO","UTF-16",100]
      But though the agentd recognizes my item key pattern:
      5680:20110617:171529.213 Adding the file [c:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\LogFiles\ReportServerService__06_17_2011_ 00_08_54.log] to logfiles.
      no data arrives to the Server.

      Comment

      • foboss
        Junior Member
        • Nov 2013
        • 7

        #18
        Anyone?

        I have the same situation: SQL Server 2008 ucs2 logfile didn't work, utf8 or ansi - perfectly.

        Zabbix Agent 2.2.0, server 2.2.0

        Comment

        • foboss
          Junior Member
          • Nov 2013
          • 7

          #19
          I've found the decision:
          Code:
          log["C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG","Error","UTF-16",100]
          It worked for me.

          Comment

          Working...