In managing network performance, user experience takes priority. Being proactive in managing performance means not only tracking the network and application, but obtaining an in-depth view of the underlying infrastructure health. There are two primary ways to obtain this information: agent or agentless.
Selecting the best method for your team requires understanding the options and selecting the solution that integrates well with your existing resources. This IT Brief will:
- Define agent and agentless approaches
- Outline pros and cons for each approach
- Establish a strategy for cost-eff ective, scalable performance visibility
DEFINING AGENT & AGENTLESS
Agents are typically proprietary software loaded onto relevant application components, devices, and servers. The question to ask application performance monitoring (APM) vendors is whether their platform requires software to be installed on your critical infrastructure.
DOES THE PLATFORM REQUIRE SOFTWARE TO BE INSTALLED ON YOUR INFRASTRUCTURE?
If the answer is “yes,” the program you’re loading is most likely an agent, which gathers data and sends it to the console or platform for analysis. Agents can also perform tasks that impact or modify the operation of the device.
DOES THE PLATFORM REQUIRE SOFTWARE TO BE INSTALLED ON YOUR INFRASTRUCTURE?
If the answer is “no,” the APM platform is likely relying upon polling technologies to acquire device performance and related application information. These solutions are typically referred to as agentless.
AGENTLESS SOLUTIONS
Agentless solutions often tap into pre-existing or native agents and reporting capabilities placed on the system or device by the infrastructure manufacturer. Utilizing intelligence from these native agents allows agentless solutions to track performance variables including power, CPU, and memory usage without aff ecting device performance. Additionally, using polling technologies like SNMP or querying Windows systems through WMI provides nearly limitless information about devices and hosted applications.
AGENT PROS & CONS
PROS
- Designed to provide critical management specific metrics
- Uses SSL or other encrypted methods to provide data
- Typically will auto-update to avoid maintenance overhead
CONS
- Can impact critical infrastructure, consuming device’s CPU, memory, and storage
- Cannot monitor beyond system on which its installed
- Time-consuming deployment requires agents for every critical device monitored
- Every new server requires additional agents be purchased
- Only tracks conditions and metrics it has been designed to target
- Cloud vendor may prohibit agents; coverage of multiple VMs can be cost prohibitive
AGENTLESS PROS & CONS
PROS
- Tracks performance without impacting devices
- Immediate device discovery and monitoring, once IP address and credentials provided
- Scales as fast as new devices can be added
- Any devices can be monitored with minimal deployment effort, not just critical devices
- Taps into cloud vendor APIs and mimics user experience via synthetic transactions
CONS
- Data sources may not provide full or relevant data
- Typically requires pre-existing services and agents to be turned on; may also require changes to firewall
- On larger networks, polling needs to be spaced out enough to avoid overlapping executions
ESTABLISHING EFFECTIVE PERFORMANCE VISIBILITY
Ultimately, each team must assess the merits of leveraging proprietary agents versus going agentless. Each has strengths and weaknesses. Many vendors now offer significant insight into the underlying health and status of the devices and network by exploiting the wealth of information infrastructure and application developers now incorporate directly into their solutions with native agents. Cloud providers as well are introducing APIs that can be readily supported by agentless solutions. This is an important point as cloud vendors generally forbid the placement of any agents within their environments.
ESTABLISHING EFFECTIVE PERFORMANCE VISIBILITY
Alternatively, if you have ready access to source code and/or require unique visibility into devices not available from agentless monitoring, then proprietary agents could be a consideration. For select applications, they can offer deep insight into application health at the expense of broad service support.
CONCLUSION
Finally, whether utilizing proprietary agents or an agentless approach, it is important to note that many solutions also provide packet-based analysis to monitor the flow of applications traversing the network. This integrated monitoring approach yields highly granular detail on the overall health of applications and infrastructure, enabling optimal operational efficiency and reduced MTTR when problems are detected.
Thanks to Network Instruments for the article.