Support Migration Notice: To update migrated JIRA cases click here to open a new case use www.vmware.com/go/sr | vFabric Hyperic 5.7.0 is Now Available

Hyperic HQ

Agent logs no performance metrics for VMs message intermittantly but vcs is collecting it fine

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Deferred
  • Affects Version/s: 4.5, 4.5.1
  • Fix Version/s: None
  • Component/s: Plugins
  • Environment:
    HQ agent running 4.5.0.1
  • Case Links:
    none
  • Regression:
    No

Description

For example:

An agent monitoring vCenter Server with 21 ESX hosts and 315 VMs is frequently logging following INFO messages. Attached is a screenshot view of the example vm (vmc-ssrc-rh54) in HQ server .Yon can see that its missing metric data for last 20 minutes.

[ssbt@vmc-ssrc-rh119 log]$ grep vmc-ssrc-rh54 agent.log
2010-11-11 21:03:21,774 INFO [pool-1-thread-28] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-11 21:51:40,812 INFO [pool-1-thread-2] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-11 21:57:20,726 INFO [pool-1-thread-21] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-11 22:10:21,112 INFO [pool-1-thread-11] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-11 22:49:40,906 INFO [pool-1-thread-4] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 01:27:01,145 INFO [pool-1-thread-3] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 01:35:41,746 INFO [pool-1-thread-4] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 01:50:01,440 INFO [pool-1-thread-7] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:12:21,876 INFO [pool-1-thread-14] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:15:41,806 INFO [pool-1-thread-21] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:20:41,656 INFO [pool-1-thread-30] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:37:41,709 INFO [pool-1-thread-27] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:48:21,925 INFO [pool-1-thread-6] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:49:41,338 INFO [pool-1-thread-27] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:57:41,506 INFO [pool-1-thread-8] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 02:59:41,647 INFO [pool-1-thread-20] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 03:04:41,656 INFO [pool-1-thread-30] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 03:06:42,032 INFO [pool-1-thread-17] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 07:55:41,220 INFO [pool-1-thread-8] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:15:20,521 INFO [pool-1-thread-1] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:36:20,709 INFO [pool-1-thread-2] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:42:20,719 INFO [pool-1-thread-18] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:44:20,580 INFO [pool-1-thread-27] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:49:20,861 INFO [pool-1-thread-7] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:52:20,860 INFO [pool-1-thread-7] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]
2010-11-12 13:53:20,931 INFO [pool-1-thread-9] [VSphereHostCollector] No performance metrics for VirtualMachine[name=vmc-ssrc-rh54, refreshRate=20, availablePerfMetric=20]

Activity

Hide
Yoav Epelman added a comment -

Bulk change to new components

Show
Yoav Epelman added a comment - Bulk change to new components
Hide
Idan Hod added a comment -

As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology.

Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix.

We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base.

This bug has been deferred as part of the new policy.

We appreciate your cooperation and continues contribution to the improvement of Hyperic.

Show
Idan Hod added a comment - As part of our continuous effort to improve product quality, The Hyperic product team has decided to implement a "zero bug policy" methodology. Following this methodology, only defects that are planned to be handled in the near future will remain open. Any other defect will be deferred, with the option to be reevaluated if the need arises, or if changes to the Hyperic road-map make such defect a candidate for a fix. We believe this new process will help create clarity and focus in the Hyperic road-map and ultimately benefit our customer base. This bug has been deferred as part of the new policy. We appreciate your cooperation and continues contribution to the improvement of Hyperic.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
    Last comment:
    42 weeks, 1 day ago