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

Disk Service Time not Collected for Windows based Servers

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Deferred
  • Affects Version/s: 4.2.0, 4.6.6, 5.0
  • Fix Version/s: None
  • Component/s: Core Monitoring
  • Environment:
    Release 4.2.0-EE build 1202,Platform:Windowsxpsp2,DB:Built-In
  • Importance:
    3-Medium
  • Case Links:
    none
  • Regression:
    Yes

Description

Steps to Reproduce:

-Navigate to Metric Data mini tab for FileServer Mount on a Widows server
-Select Show All Metrics

  • Enable 'Disk Service Time'

Wait a few collection cycles and notice that the metric is never collected.

Actual Results:

I enable Metric around 9:00 AM at around noon Metric were not collected (for 1 minute interval)

Issue Links

Activity

Hide
Ryan Morgan added a comment -

Environment states Windows XP SP2, need to also support Windows 2003.

Show
Ryan Morgan added a comment - Environment states Windows XP SP2, need to also support Windows 2003.
Hide
David Wiener added a comment -

Closed due to being outdated

Show
David Wiener added a comment - Closed due to being outdated
Hide
Edward Gonzales added a comment -

Re-opening HHQ-3385. It was closed because it was old, but the problem still exists and we have another customer who opened an issue for this.

Show
Edward Gonzales added a comment - Re-opening HHQ-3385. It was closed because it was old, but the problem still exists and we have another customer who opened an issue for this.
Hide
Edward Gonzales added a comment -

Looks like SIGAR-65 is the reason. It looks like it's never been added to SIGAR to collect this from HP-UX or Windows. This would either need to be added to Sigar or a direct Windows command would probably need to be added to hq-plugin.xml

Show
Edward Gonzales added a comment - Looks like SIGAR-65 is the reason. It looks like it's never been added to SIGAR to collect this from HP-UX or Windows. This would either need to be added to Sigar or a direct Windows command would probably need to be added to hq-plugin.xml
Hide
Yaron Borenstein added a comment -

The command is on hq-plugin.xml,
it looks like Sigar issue:

07-02-2013 13:27:02,923 IST WARN [system-0] [ScheduleThread@592] Collection of metric: 'FileServer Mount:sigar:Type=MountedFileSystemUsage,Arg=C%3A\:DiskServiceTime' took: 2872ms

Show
Yaron Borenstein added a comment - The command is on hq-plugin.xml, it looks like Sigar issue: 07-02-2013 13:27:02,923 IST WARN [system-0] [ScheduleThread@592] Collection of metric: 'FileServer Mount:sigar:Type=MountedFileSystemUsage,Arg=C%3A\:DiskServiceTime' took: 2872ms
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 (1)
Watch (2)

Dates

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