Monitoring build resources with the TFS 2017 management pack

This post announces that the TFS 2017 management pack no longer supports monitoring of build resources (XAML controllers/agents, Build/Release agents). It details the historical approaches to build resource monitoring within TFS management packs and explains the decision to abandon this in TFS 2017 due to complexity and the availability of equivalent monitoring in System Center. The post provides a recommended approach for monitoring build resources using System Center's built-in capabilities: monitoring machine availability, creating Windows Service monitors for XAML build resources (e.g., TFSBuildServiceHost.2013), and creating process monitors for Build/Release resources (e.g., Agent.Listener.exe) with specific machine groups. This new approach allows for monitoring interactive agents, Linux agents, and setting custom thresholds for CPU/memory consumption.
More from the Azure Pipelines Agent Operating System Support trail
- April Patches for Azure DevOps Server and Team Foundation Server
- CDN Domain URL change for Agents in Pipelines
- Announcing the General Availability of Managed DevOps Pools (MDP) for Azure DevOps
- Announcing Public Preview of Managed DevOps Pools (MDP) for Azure DevOps
- End of support for Azure Pipelines agents running on CentOS 6, Debian 4.9, Fedora 32, Ubuntu 16, macOS 10.14, and older versions