In EGIT, monitoring performance of IT resources must be anchored to what the business expects and has formally agreed to receive—i.e., service level requirements. Performance that is not measured against defined service levels risks optimizing technical metrics while missing stakeholder outcomes (availability, response time, capacity, support targets, etc.). COBIT emphasizes managing and monitoring service agreements and reporting service levels as a core management practice, because service levels translate business needs into measurable targets and enable consistent governance oversight and accountability.

End-user feedback (A) is valuable but subjective and may lag behind systemic issues; it complements, not replaces, defined service targets. A business impact analysis (B) is critical for continuity planning and prioritization, but it’s not the primary instrument for day-to-day performance monitoring of IT resources. Centralized log analysis (C) is a technical capability that supports detection and troubleshooting, yet logs do not define “good performance” without a benchmark; service level requirements provide that benchmark. From a governance standpoint, service levels allow management to evaluate whether IT resources are delivering expected performance and value to stakeholders, enabling corrective actions and continual improvement aligned to enterprise goals.

========