Ad Widget

Collapse

Windows Agent Limitation?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rolandsym
    Member
    • Jul 2007
    • 76

    #1

    Windows Agent Limitation?

    Hi,
    I've been trying to push some text information up to zabbix from a windows machine. I just want a simple screen where I see the running processes for the windows machine. I have the output and zabbix recognizes it. The problem comes down to zabbix server not getting the full output.

    My log file for the zabbix agent shows that it is sending the full output but when I view the server log it is only showing 255 characters for that value. Which is what it shows when I look at the value on the frontend. I want the whole output. I don't want it truncated. Now is this a server or client limitation on the passing of data? I'm using zabbix 1.4.1 on ubuntu with 1.4.1 client.

    Any help or direction would be appreciated.

    Rolandsym
  • bbrendon
    Senior Member
    • Sep 2005
    • 870

    #2
    Dunno if this is possible. I think it is according to the developers. Even if it is, I don't zabbix is the proper place to be doing this, but each to their own.

    If you do get it to work, I think you'll need the "type of information" for the item set to text.

    Good luck. Text is new in 1.4.1 and I haven't tried it.
    Unofficial Zabbix Expert
    Blog, Corporate Site

    Comment

    • Alexei
      Founder, CEO
      Zabbix Certified Trainer
      Zabbix Certified SpecialistZabbix Certified Professional
      • Sep 2004
      • 5654

      #3
      This is fixed in pre-1.4.2. ZABBIX properly displays information of type text in screens, so you may have a nice "top"-like view of processes, for example.
      Alexei Vladishev
      Creator of Zabbix, Product manager
      New York | Tokyo | Riga
      My Twitter

      Comment

      • rolandsym
        Member
        • Jul 2007
        • 76

        #4
        Yesterday?

        I re-installed zabbix on my test server Tuesday with Monday nights pre-1.4.2 build and I am still a getting the same issue and used the pre-1.4.2 client on the test machine. Was it fixed Last night?(August 15th's build?)

        Rolandsym

        Comment

        Working...