Free Server Performance Monitoring
STOR2RRD

6.02

It fixes a few issues that appeared in 6.00 and adds a few small enhancements.

Enhancements

  • Re-grouping: new view, where all graphs from all tabs are sorted into 4 tabs (daily/weekly/monthly/yearly)
  • Solaris: Custom Group implementation, Zones and LDOM/CDOM separately, CPU core and Memory used
  • Solaris: aggregated total CPU/memory with all LDOM/CDOM on the top of Solaris section
  • XenServer: expanded Configuration data
  • Alerting implemented for stand-alone Linux servers (not under any virtualization)
  • ACL: introduced read-only role, members can see everything but cannot modify anything

Fixes

  • VMware: if no cluster was defined, there was a problem with presenting ESXi in the menu, fixed
  • VMware: fix for this error: "SOAP request error - possibly a protocol issue: 500 read timeout"
  • IBM Power Systems: HMC REST API : many smaller fixes, upgrade to it if you have any problem
  • IBM Power Systems: SDMC/FSM support: CPU pool utilisation stopped after 6.00, fixed
  • oVirt/RHV: fixed a few smaller issues
  • Reporter: if ACL in place then the first defined item in the report has been skipped, fixed
  • AIX: LPAR2RRD server on AIX might core dump in load.sh, fixed
  • OS agent: NFS mount caused a problem to the agent, fixed
  • Microsoft Hyper-V: fix of a wrong path added in crontab after install/upgrade

6.00

Main news are support for new virtualization technologies and HMC REST API support.

Supported virtualization technologies

IBM Power Systems

  • HMC REST API usage as a total replacement for HMC CLI (ssh) access used until now
    • Performance data for all physical adapters: SR-IOV, FC, Eth, SAS
    • Configuration with more details
    • Power Enterprise Pools configuration
  • POWER9 support in CPU Workload Estimator
  • Monitoring and alerting for filesystem space utilization
  • IBM i - ASP latency monitoring
  • Reporter - new reporting feature
  • AIX WLM (Workload Manager) monitoring

VMware

  • New reporting feature called Reporter
  • Cluster LAN aggregated graphs (per ESXi)
  • Custom Group: Memory consumed added
  • Optimized data gathering from vCenter and back-end processing