Softpedia >Windows >Network Tools >Network Monitoring >vFoglight Pro >  Changelog

vFoglight Pro Changelog

What's new in vFoglight Pro 6.7.1

Mar 12, 2013
  • vFoglight 6.7.1 now supports vSphere 5.1 as well as Hyper-V on Windows 2012. Users upgrading from previous versions of vFoglight must upgrade existing agents to enable these features.
  • Resolved Issues and Enhancements:
  • Management server:
  • Session memory leak in Hyper-V agent fixed.
  • Improved the host identity uniqueness, when different hosts with the same hostname (BIOS and MAC addresses) are deployed to the same virtual infrastructure.
  • The dependency from the host through the VMware Virtual Machine disconnected, causing two identical objects to display.
  • Edits to rules do not take effect until after the Management Server is restarted. This affects Management Server versions 5.6.2 and 5.6.3.
  • An issue in the handling of rollup of observations can lead to complete loss of data in the long-term generation.
  • Timeouts in communication between Federation Master and Federated Child can cause alarm email-notifications to be resent if they are configured for services on the Master.
  • Browser Interface:
  • Improved performance on the Cluster Capacity dashboard.
  • Improved performance on the VMware Explorer VM Summary tab.
  • Improved performance on the VMware Explorer VM Monitor tab.
  • When a rule is configured to use an Alarm Association and it fires an alarm, viewing that alarm opens the new Alarm Detail Dialog. If the rule also generates an email, or if a service that is configured to send emails is triggered by the alarm, the generated email contains a URL that should link to the new Alarm Detail Dialog. However, in Foglight 5.6.3, there was an issue in the handling of this URL which caused the user to be directed to an error page instead of the new Alarm Detail Dialog.
  • When selecting objects to blackout, children of the selected object are now automatically being selected. This can lead to more objects being blacked out then intended. For example, if you blackout a service, all the objects in the service are automatically blacked out as well. The check box at the bottom of the object selection page is intended to offer the option to select all objects, but the state of the checkbox is currently being ignored.
  • The function script text is loaded from the PersistenceService on each invocation, causing performance issues.
  • Metric charts on custom dashboards do not render correctly when the "Only show axis of selected metric" option is selected.
  • When adding a parameterized shared Metric or Portlet Wrapper view to a custom dashboard, an issue occurs if the view does not use the auto-height setting.