Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-12990

VMware Datastore usage mismatch

          Details

          • Type: Incident report
          • Status: Closed
          • Priority: Major
          • Resolution: Fixed
          • Affects Version/s: 3.2.7
          • Fix Version/s: 3.0.19rc1, 3.4.11rc1, 4.0.0alpha8, 4.0 (plan)
          • Component/s: Proxy (P), Server (S)
          • Labels:
          • Environment:
            Debian 3.16.0-4-amd64, mysql Ver 15.1 Distrib 10.0.30-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2, 2 VCPU, 4GB RAM, VMware ESXi 5.5.0 build-2068190.
          • Team:
            Team C
          • Sprint:
            Sprint 33, Sprint 34, Sprint 35
          • Story Points:
            1

            Description

            Steps to reproduce:
            On VMWare host, create a VM snapshot.

            Result:
            The used space did not change when the snapshot create the files on the datastore.

            Expected:
            The Zabbix monitoring (attached image) must follow the VMWare monitoring(attached image).

              Attachments

                Issue Links

                caused by

                Problem report - Problem report ZBX-15417 VMWare datastore monitoring loses *all* history and trends when Zabbix can't get the data once

                • Major - Major loss of function.
                • Closed
                causes

                Problem report - Problem report ZBX-15142 LC_ALL=en_US.UTF-8 locale on server causes issue for vmware monitoring - Cannot parse DateTime value

                • Blocker - Blocks development and/or testing work, production could not run.
                • Closed

                Problem report - Problem report ZBX-14677 wmvare monitoring (datastore,NIC,performace counter...) failed after 3.4.8

                • Critical - Crashes, loss of data, severe memory leak.
                • Closed

                Problem report - Problem report ZBX-14548 cannot get refresh rate for Datastore. A specified parameter was not correct.

                • Trivial - Cosmetic problem like misspelt words or misaligned text.
                • Closed

                  Activity

                    People

                    • Assignee:
                      MVekslers Michael Veksler
                      Reporter:
                      incoquinita Érick Rangel Gomes
                    • Votes:
                      0 Vote for this issue
                      Watchers:
                      7 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved: