logo

Agent vs Agentless Monitoring: Why We Chose Agentless | UpGuard

ID: 178ee15b-7ec2-529d-a3be-251c8ffb7deb

STIX ID: report--178ee15b-7ec2-529d-a3be-251c8ffb7deb

Feed Name: UpGuard Blog

Date Published: 2024-09-17

Date Updated: 2026-05-01

...
...

UpGuard announces a move from a JRuby agent to an agentless Go-based connection manager, citing lower maintenance costs, significantly improved performance and memory efficiency, and easier on-premise deployments; it argues that for configuration monitoring, API-based agentless access is sufficient, addresses concerns around sampling and platform support, and positions the new architecture as a faster, lighter, broadly compatible solution.

Your team is not currently subscribed to this feed. You must subscribe to it in order to see this post.