Radar: connect with agents - #3955
Conversation
🧠 Redis MemoryFound 9 related items from repository history (1 new this commit):
Memory updated at 2bf5eaa |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 9251adf. Configure here.
dwdougherty
left a comment
There was a problem hiding this comment.
Apart from the Bugbot issue and the TODO you have in a comment, the language looks good to me. One nitpick: the first image, activate-managed-agent.png could do with a bit of trimming.

Note
Low Risk
Documentation-only changes with no application code, credentials handling, or deployment logic modified in this PR.
Overview
Documents Radar agents for Redis Software and Redis Open Source when Radar cannot reach clusters directly (firewalls, private subnets, air-gapped paths).
Adds
agent.md, a new operate guide that explains managed vs static credential modes, tarball install and systemd setup, managed activation and static YAML provisioning, private CA trust, isolated-network export/submit-export, monitoring (/healthz,/metrics), security notes, and upgrade/removal. It references new UI screenshots underimages/radar/.Updates
_index.mdandconnect.mdso network reachability is called out as a setup requirement, with links to the agent page when direct outbound access from Radar is not possible.Reviewed by Cursor Bugbot for commit 2bf5eaa. Bugbot is set up for automated code reviews on this repo. Configure here.