Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions content/operate/radar/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,7 @@ Radar reads each cluster's management interface using credentials you supply, th
This approach has two significant consequences:

- **Radar needs credentials for every cluster you want to see.** Getting that access in place is most of the setup work. See [Connect clusters]({{< relref "/operate/radar/connect" >}}).
- **Radar must be able to reach each cluster.** Where it can't, such as a cluster behind a firewall or on an isolated network, an agent you install inside that network collects and submits on Radar's behalf. See [Connect clusters with an agent]({{< relref "/operate/radar/agent" >}}).
- **Radar shows the last successful state collection rather than live state.** Radar collects the state of every connected cluster — Redis Software, Redis Open Source, Redis Cloud, Amazon ElastiCache, and Google Memorystore — on a fixed interval, so a value is only as fresh as the last time Radar reached that cluster. Radar shows that age alongside the data.

## Next steps
Expand Down
385 changes: 385 additions & 0 deletions content/operate/radar/agent.md

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion content/operate/radar/connect.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ Connect Redis Software clusters and Redis Open Source instances that you run you
For every connection you need:

- **Credentials for the cluster or instance.** Radar uses the same management interface you do, so it needs an account there. Read access is enough.
- **Network access from Radar to the source.** Radar connects outbound. Nothing needs to connect back to Radar, so no inbound rule is required on the Radar host.
- **Network access from Radar to the source.** Radar connects outbound. Nothing needs to connect back to Radar, so no inbound rule is required on the Radar host. If Radar can't reach a cluster directly, install an agent inside that network instead. See [Connect clusters with an agent]({{< relref "/operate/radar/agent" >}}).

### Connect a Redis Software cluster

Expand Down
29 changes: 29 additions & 0 deletions content/operate/radar/release-notes/2026-9-5.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,29 @@
---
title: Redis Radar release notes 2026.9.5
alwaysopen: false
categories:
- docs
- operate
- radar
description: Connect clusters that Radar can't reach directly by installing an agent.
linkTitle: 2026.9.5
weight: 9
tags:
- self-managed
---

Radar can now collect from clusters it can't reach directly. You install an agent on a host inside the network that holds them, and the agent opens an outbound connection to Radar.

This is a Short-Term Support (STS) release. See [Self-managed releases]({{< relref "/operate/radar/release-notes" >}}#self-managed-releases) for more details.

## Highlights

### Connect clusters with an agent

- Collect from **Redis Software** and **Redis Open Source** clusters behind a firewall, in a private subnet, or on a segmented network. Radar needs no inbound access to your network.
- Choose between two modes. **Managed** agents receive source credentials from Radar, so you add and change sources from the Radar UI. **Static** agents read their sources from a file on the agent host, so those credentials never leave it.
- Collect from a fully isolated network by exporting to a file on one host and submitting it from another.
- Install from standalone agent packages for Linux on amd64 and arm64, including Federal Information Processing Standards (FIPS) 140-3 builds.
- Track every agent under **Settings > Agents** and in the **Connected agents** list on the Connections page, with its mode, platform, version, and last heartbeat.

Radar accepts agent connections on its agent gRPC endpoint, which isn't enabled on every Radar deployment. See [Connect clusters with an agent]({{< relref "/operate/radar/agent" >}}).
7 changes: 4 additions & 3 deletions content/operate/radar/release-notes/_index.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,7 @@ STS releases receive security and bug fixes for 6 months after release. LTS rele

Install a new release when you're ready to upgrade. See [Install Radar]({{< relref "/operate/radar/install" >}}).

| Release | Support track | What changed |
|--------------------------------------------------------------------|---------------|------------------|
| [2026.9.2]({{< relref "/operate/radar/release-notes/2026-9-2" >}}) | STS | Initial release. |
| Release | Support track | What changed |
|--------------------------------------------------------------------|---------------|--------------------------------------|
| [2026.9.5]({{< relref "/operate/radar/release-notes/2026-9-5" >}}) | STS | Connect clusters with an agent. |
| [2026.9.2]({{< relref "/operate/radar/release-notes/2026-9-2" >}}) | STS | Initial release. |
Binary file added static/images/radar/activate-managed-agent.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/radar/connections-with-agents.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/radar/settings-access-keys.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added static/images/radar/settings-agents.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading