CA eHealth Performance Manager 6.1 Report Project Sample Requirements
April 17, 2012Some of the possible Sample Report outputs.
Sample Report Produce By Ca’s eHealth Suites
- MPLS Bandwidth Utilization
- Bandwidth Utilization In / Out (Wan – Fqdn-Serial0/0)
Server Utilization
- CPU Utilization
- Total Network (frames / second)
- Top 10 Partitions (utilization)
- Service Performance
- DNS Lookups
- TCP Connections per second
Application Response
- Average Response time (msec)
- Average Response time (bytes / second)
- Quality Attributes
- Reliability
With configuration tuning, eHealth is capable of scaling upwards of several thousand elements per single management server. Furthermore, eHealth management servers can be arranged in a distributed environment, providing virtually a limitless ceiling on the number of nodes that can be managed in client environments.
Availability
- All management servers will be a part of company wide backup solution for complete and incremental backups, which also provide backups for “open files” and databases.
This solution defines a high availability design which deploys a failover strategy, as a vital part of availability. CA Best Practice recommends that the primary and backup eHealth servers be installed in a Cluster Environment.
Best Practices approach
- This solution is architected to meet ITIL Availability and Capacity Management disciplines as well as CA Best Practice.
- Architecture approach
This solution establishes a solid monitoring and performance management foundation for both servers and network. A phased implementation approach is recommended to first establish monitoring and fault management systems. Second phase include performance monitoring for both servers and network. Solutions high-availability should be a future consideration.