Ad Widget

Collapse

VmBix: vsphere monitoring

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • aigars
    Member
    • Apr 2010
    • 55

    #31
    Hi,

    I'm not Linux expert and maybe somebody can help. When I tried to lunch service on debian linux I get error:

    $Starting vmbixd: /etc/init.d/vmbixd: 103: daemon: not found
    Last edited by aigars; 28-06-2013, 14:45.

    Comment

    • gavind
      Member
      • Mar 2013
      • 59

      #32
      With that error message, I would say that it hasn't been installed properly. It's trying to look for the daemon.

      Comment

      • aigars
        Member
        • Apr 2010
        • 55

        #33
        I found so init script is different for Debian OS. Problem is fixed

        Comment

        • code42
          Junior Member
          • Aug 2013
          • 4

          #34
          Init script trouble with OpenSuse

          Hi guys.

          I try to use Vmbix to monitor my ESX.

          Zabbix is used through the Zabbix-Appliance 2.0.6 , which is based on OpenSuse 12.2 Linux OS.


          The original vmbixd init script calls the daemon function. (You know, that /etc/init.d/vmbixd: line 37: daemon: command not found output)
          Unfortunately this one is not implemented in OpenSuse (a licence problem i have found through the internet ).

          I tried the one used for Debian servers , but as i thought it did not work too.
          I don't know how to built an init script for Opensuse (nor from any OS )

          Did someone solved it and may share a working vmbixd init script with us please ?

          Comment

          • mcxian
            Junior Member
            • Mar 2013
            • 10

            #35
            Support for ESXi 5.1?

            We just installed VIMbix, but I'm not sure we should configure it to point to. In ESXi 5.1, the roles the vcenter server performed are now broken up into multiple servers.

            If I configure the daemon to talk to our vsphere server, the log states:
            I, [2013-09-25T14:46:17.134014 #4419] INFO -- : XXX.XXX.XXX.XXX: connected
            I, [2013-09-25T14:46:17.134116 #4419] INFO -- : XXX.XXX.XXX.XXX: data collection started
            E, [2013-09-25T14:46:17.195384 #4419] ERROR -- : XXX.XXX.XXX.XXX: Execution timed out (0 seconds)


            If I point to the inventory server, I see:
            >> Writing PID to var/run/vimbix.pid
            >> Thin web server (v1.5.1 codename Straight Razor)
            >> Maximum connections set to 1024
            >> Listening on 0.0.0.0:9090, CTRL+C to stop
            I, [2013-09-25T14:46:16.642785 #4419] INFO -- : XXX.XXX.XXX.XXX: File datadump_XXX.XXX.XXX.XXX saved

            Which looks okay, but the contents of the file are:
            {"virtualmachines":{},"hosts":{},"viserver":{"coll ectionduration":"0","timestampcheck":"1380139276", "status":"FAILED"},"datastores":{}}



            So I'm not sure if I just don't have the necessary permissions to view the ESXi environment, or if I'm attempting to contact the wrong server. There may also be some firewall ports that need to be opened between my zabbix server and the vsphere environment. Does anyone have any ideas?

            Comment

            • hryamzik
              Junior Member
              • Dec 2011
              • 16

              #36
              I didn't work with vsphere 5, but looks like you should use the server you connect your vsphere client to. VmBix uses the same protocol as native client does.

              Comment

              • mcxian
                Junior Member
                • Mar 2013
                • 10

                #37
                So I'm not sure if I just don't have the necessary permissions to view the ESXi environment
                Yep! That was the problem

                The template import failed to where I had to remove the graph prototypes to get it going. Now I've got checks on the ESX servers, but not the VMs on them.

                So now I'm just not sure why VM enumeration is failing. The json file for discovery appears to be okay, and I don't see any errors about it. Is it possible zabbix has a line limit on accepting json discovery files?

                Comment

                • magajna
                  Junior Member
                  • Sep 2013
                  • 6

                  #38
                  Can this scripts be used for ESXi free version?

                  Comment

                  • magajna
                    Junior Member
                    • Sep 2013
                    • 6

                    #39
                    Originally posted by code42
                    Hi guys.

                    I try to use Vmbix to monitor my ESX.

                    Zabbix is used through the Zabbix-Appliance 2.0.6 , which is based on OpenSuse 12.2 Linux OS.


                    The original vmbixd init script calls the daemon function. (You know, that /etc/init.d/vmbixd: line 37: daemon: command not found output)
                    Unfortunately this one is not implemented in OpenSuse (a licence problem i have found through the internet ).

                    I tried the one used for Debian servers , but as i thought it did not work too.
                    I don't know how to built an init script for Opensuse (nor from any OS )

                    Did someone solved it and may share a working vmbixd init script with us please ?
                    Try this...

                    Insted of this daemon $program "-c '$configfile' -f '$pidfile'" use startproc $program "-c '$configfile' -f '$pidfile'"

                    Comment

                    • magajna
                      Junior Member
                      • Sep 2013
                      • 6

                      #40
                      Why can't i start LSB on zabbix? Have openSUSE system...
                      Attached Files

                      Comment

                      • Saichovsky
                        Junior Member
                        • Nov 2013
                        • 5

                        #41
                        Awesome tool

                        Hi hryamzik,

                        I must commend you for the good job done on VmBix. I'm just thinking of extending it by adding autodiscovery to the templates. Could anyone be familiar with creation of autodiscovery prototypes? There seems to be lack of examples on the intertubes. What I get from looking around is not detailed enough.

                        More suggetions welcome ;-)

                        Thanks guys

                        Comment

                        • aigars
                          Member
                          • Apr 2010
                          • 55

                          #42
                          I think you can use native VMware monitoring in v.2.2. I switched from VmBix to zabbix native vmware monitoring and it's super cool

                          Comment

                          • Saichovsky
                            Junior Member
                            • Nov 2013
                            • 5

                            #43
                            native VMWare monitoring

                            Hi aigars,

                            I'm not familiar with VMware. Kindly advise on what this native vmware is and how I can access it.

                            Thanks,

                            S.

                            Comment

                            • aigars
                              Member
                              • Apr 2010
                              • 55

                              #44
                              Hi,

                              First of all you must install zabbix 2.2! Then you can read this paper https://www.zabbix.com/documentation.../vm_monitoring

                              It's easy to setup LLD for VMware virtual machines.
                              1) Create dedicated user in virtualcenter for monitoring. Give read-only rights.
                              2) Create host which is your virtualcenter.
                              3) Define macros in this host(user, password and vcenter link)
                              4) Assign templates which already is present in v2.2 for LLD vmware discovery.

                              Process will start and you should wait little bit to discovery complete. After that you can tune your templates or create new ones.

                              Code:
                              Host configuration
                              
                              To use VMware simple checks the host must have the following user macros defined:
                              
                              {$URL} - VMware service (vCenter or vSphere) SDK URL (https://servername/sdk).
                              {$USERNAME} - VMware service user name
                              {$PASSWORD} - VMware service {$USERNAME} user passsword

                              Comment

                              • tatapoum
                                Senior Member
                                • Jan 2014
                                • 185

                                #45
                                Hi,

                                VMBIX is really the best way to monitor a VMWare environment with Zabbix.

                                Zabbix 2.2 lacks a lot of interesting VMWare items, so I have improved VMBIX in version 1.0.2 with a few other checks. My code is bad but it works, with great performance (my server is at 10% CPU with 50 items/s).

                                This is a BSD 3 license, so I think I can provide the code.

                                Here is the list of the checks (you can see them using "java -jar vmbix.jar") :
                                Code:
                                about[*]
                                datastore.discovery[*]
                                datastore.size[name,free]
                                datastore.size[name,total]
                                esx.connection[name]
                                esx.cpu.load[name,cores]
                                esx.cpu.load[name,total]
                                esx.cpu.load[name,used]
                                esx.discovery[*]
                                esx.maintenance[name]
                                esx.memory[name,total]
                                esx.memory[name,used]
                                esx.path[name,active]
                                esx.path[name,dead]
                                esx.path[name,disabled]
                                esx.path[name,standby]
                                esx.status[name]
                                esx.vms.memory[name,active]
                                esx.vms.memory[name,balooned]
                                esx.vms.memory[name,compressed]
                                esx.vms.memory[name,consumed]
                                esx.vms.memory[name,overheadConsumed]
                                esx.vms.memory[name,private]
                                esx.vms.memory[name,shared]
                                esx.vms.memory[name,swapped]
                                event.latest[*]
                                perf.counters[name]
                                ping[*]
                                vm.consolidation[name,needed]
                                vm.cpu.load[name,cores]
                                vm.cpu.load[name,total]
                                vm.cpu.load[name,used]
                                vm.discovery[*]
                                vm.folder[name]
                                vm.guest.disk.all[name]
                                vm.guest.disk.capacity[name,disk]
                                vm.guest.disk.free[name,disk]
                                vm.guest.ip[name]
                                vm.guest.name[name]
                                vm.guest.os[name]
                                vm.guest.tools.mounted[name]
                                vm.guest.tools.running[name]
                                vm.guest.tools.version[name]
                                vm.host[name]
                                vm.memory[name,active]
                                vm.memory[name,balooned]
                                vm.memory[name,compressed]
                                vm.memory[name,consumed]
                                vm.memory[name,overheadConsumed]
                                vm.memory[name,private]
                                vm.memory[name,shared]
                                vm.memory[name,swapped]
                                vm.memory[name,total]
                                vm.perf.counter[name,counter,[instance,interval]]
                                vm.powerstate[name]
                                vm.status[name]
                                vm.storage.committed[name]
                                vm.storage.uncommitted[name]
                                vm.storage.unshared[name]
                                I particularly have added support for the VMWare Performance Manager. So, you can now query the cpu.ready or disk.queueLatency for example :
                                Code:
                                # zabbix_get -s localhost -p 12050 -k vm.perf.counter[VMNAME,cpu.ready]
                                418
                                # zabbix_get -s localhost -p 12050 -k vm.perf.counter[VMNAME,cpu.ready,,3600]
                                4910
                                I also have added LLD discovery for hosts, VMs and datastores :
                                Code:
                                # zabbix_get -s localhost -p 12050 -k esx.discovery[*]
                                {"data":[{"{#ESXHOST}":"esx7.domain.local"},{"{#ESXHOST}":"esx8.domain.local"},{"{#ESXHOST}":"esx6.domain.local"},{"{#ESXHOST}":"esx5.domain.local"}]}
                                Let me know if you find this useful or if you need some new items. Here is the code (it needs gson : https://code.google.com/p/google-gson/).

                                dav3860
                                Attached Files
                                Last edited by tatapoum; 25-04-2014, 13:59.

                                Comment

                                Working...