Ad Widget

Collapse

External Script - no vlaues

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • dorsepp
    Junior Member
    • Oct 2013
    • 9
    #1

    External Script - no vlaues

    Hi all,

    I have a problem with my zabbix 2.0.8. I try to use an external python script which give me the values from an ESX-Server via CIM - API. If I execute the script on the zabbix console everything is fine, but when I try to use an item I get no value back. I tryed to fix the problem with changing the "Type of Information" but there was no affect. I changed the debuglevel to 4 but i can´t find the transfered command in the log. The item comes not to "not supported".
    I checked the sytax for the key too. The executable script is named cim.esx and my zabbix-user have access.
    So the key is cmi.esx["parameter"]. The interface is named xxx.xxx.xxx.xxx:10051 but i don´t know the port is transfered and the problem is there.

    So is there a possibilty to see the realy transfered command to fix this problem?
    Do somenone have the same problem with this zabbixversion and annother external script?

    I hope someone can help me and sorry for the bad english.

    Thanks in advance.

    Greetings Sepp
    Tags: None
    • steveboyson
      Senior Member
      • Jul 2013
      • 582
      #2
      It's probably a timeout issue. Querying ESX servers is a pretty time consuming thing.
      I would suggest to redirect output to a text file, schedule this via cron and create an external script which just greps out the relevant information out of this file.

        Comment

        • dorsepp
          Junior Member
          • Oct 2013
          • 9
          #3
          Thank you for the quick answer. After few hours I found the reason for the issue.

          I have to insert a second parameter for the script. It´s not cim.esx["parameter"], it´s cim.esx["{HOST.CONN}","parameter"].

          I have done it with an how to from lab4.org. It´s possible the how to works with an older version of zabbix.

          Now everything is fine and with our vSphere Farm with different Hardware it is much easier to monitor. IPMI is a much better way for this reason. It works fast, but with ILO3 there are not enough values.

          Thanks for your help

            Comment

            • gavind
              Member
              • Mar 2013
              • 59
              #4
              I have to insert a second parameter for the script. It´s not cim.esx["parameter"], it´s cim.esx["{HOST.CONN}","parameter"].
              Thanks for pointing that out. I'll keep that in mind.

                Comment

                Previous template Next
                Working...