Deployment Types
Radar Agent supports multiple Redis deployment types. Each type has specific configuration requirements.
Standalone Deployments
Monitor single Redis instances.
Configuration
deployments:
- id: "cache-01"
name: "cache-server"
type: "standalone"
redis_url: "redis://redis.example.com:6379"
credentials:
password: "${REDIS_PASSWORD}" # Optional
For TLS connections:
deployments:
- id: "cache-tls-01"
name: "cache-server-tls"
type: "standalone"
redis_url: "rediss://redis.example.com:6380" # rediss:// for TLS
credentials:
password: "${REDIS_PASSWORD}"
Environment Variables
# When only one standalone deployment exists
export REDIS_HOST=localhost
export REDIS_PORT=6379
export REDIS_PASSWORD=mypassword
Data Collected
- Server info (version, uptime, memory)
- Configuration settings
- Client connections
- Replication status
- Persistence info (RDB/AOF)
- Performance metrics
Enterprise Deployments
Monitor Redis Enterprise clusters via REST API.
Configuration
deployments:
- id: "ent-prod"
name: "production-enterprise"
type: "enterprise" # Case-insensitive
rest_api:
host: "enterprise.example.com"
port: 9443
use_tls: true
insecure: false # Set true for self-signed certs
enterprise_admin_url: "https://enterprise.example.com:8443" # Optional UI URL
enterprise:
db_endpoint: "external_ip" # Options: external_ip, internal_ip, dns (default: external_ip)
credentials:
rest_api:
basic_auth: "admin@redis.local:${ENTERPRISE_PASSWORD}"
Fields Explained
rest_api section (top-level, required):
host
: REST API hostname or IP addressport
: REST API port (typically 9443)use_tls
: Whether to use HTTPS (typically true for production)insecure
: Set totrue
to skip certificate verification for self-signed certificatesenterprise_admin_url
: Optional UI URL for reference only (not used for data collection)
enterprise section (top-level, optional):
db_endpoint
: How to report database endpoints -external_ip
(default),internal_ip
, ordns
credentials.rest_api (required):
basic_auth
: Authentication inusername:password
format (e.g.,"admin@cluster.local:password123"
)
Alternative Configuration (Compatibility)
For backward compatibility, enterprise_api
is also supported as an alias for rest_api
in the credentials section:
deployments:
- id: "ent-prod"
name: "production-enterprise"
type: "enterprise"
rest_api:
host: "enterprise.example.com"
port: 9443
use_tls: true
insecure: true
credentials:
enterprise_api: # Alternative to rest_api (both work)
basic_auth: "admin@redis.local:${ENTERPRISE_PASSWORD}"
Environment Variables
# Override by deployment ID (uses uppercased ID with underscores)
export RADAR_ENTERPRISE_ENT_PROD_REST_API_URL=https://new-url:9443
export RADAR_ENTERPRISE_ENT_PROD_USERNAME=admin@redis.local
export RADAR_ENTERPRISE_ENT_PROD_PASSWORD=newpassword
export RADAR_ENTERPRISE_ENT_PROD_INSECURE=true
Data Collected
- Cluster topology and nodes
- Database configurations
- License information
- Memory and storage metrics
- Replication status
- Module information
Cluster Deployments
Monitor Redis OSS clusters with automatic node discovery.
Configuration
deployments:
- id: "cluster-01"
name: "main-cluster"
type: "cluster" # Case-insensitive
redis_urls:
- "cluster1.example.com:7000"
- "cluster2.example.com:7000"
- "cluster3.example.com:7000"
credentials:
password: "${CLUSTER_PASSWORD}" # Optional
Note: The agent automatically discovers all cluster nodes from the seed nodes specified in redis_urls
.
Discovery
- Connects to seed nodes
- Runs
CLUSTER NODES
to discover topology - Collects from all discovered nodes
- Handles node failures gracefully
Data Collected
- Full cluster topology
- Slot distribution
- Node roles (master/replica)
- Node health status
- Per-node metrics (memory, clients, ops)
- Cluster-wide statistics
Sentinel Deployments
Monitor Redis high-availability setups with Sentinel.
Configuration
deployments:
- id: "sentinel-01"
name: "ha-redis"
type: "sentinel" # Case-insensitive
master_name: "mymaster"
sentinel_urls:
- "sentinel1.example.com:26379"
- "sentinel2.example.com:26379"
- "sentinel3.example.com:26379"
credentials:
password: "${REDIS_PASSWORD}" # Redis instance password
sentinel_password: "${SENTINEL_PASSWORD}" # Sentinel password (if different)
Discovery
- Connects to Sentinels
- Discovers monitored masters
- Finds replicas for each master
- Handles Sentinel failures with fallback
Data Collected
- Sentinel instances and status
- Monitored masters
- Replica information
- Failover history
- Quorum configuration
- Master/replica Redis metrics
Multiple Deployments
Monitor multiple deployments of different types:
agent:
id: radar-agent-001
server:
grpc_url: https://grpc.radar.redis.io:443 # Production Radar gRPC endpoint
api_key: ${RADAR_API_KEY}
deployments:
# Enterprise cluster
- id: ent-01
name: enterprise-prod
type: enterprise
rest_api:
host: enterprise.local
port: 9443
use_tls: true
insecure: true # For self-signed certs
enterprise:
db_endpoint: external_ip
credentials:
rest_api:
basic_auth: "admin@redis.local:${ENT_PASSWORD}"
# Standalone cache
- id: cache-01
name: session-cache
type: standalone
redis_url: redis://cache.local:6379
credentials:
password: ${CACHE_PASSWORD}
# Redis Cluster
- id: cluster-01
name: data-cluster
type: cluster
redis_urls:
- node1.local:7000
- node2.local:7000
- node3.local:7000
credentials:
password: ${CLUSTER_PASSWORD}
# Sentinel HA
- id: sentinel-01
name: ha-redis
type: sentinel
master_name: mymaster
sentinel_urls:
- sentinel1.local:26379
- sentinel2.local:26379
credentials:
password: ${REDIS_PASSWORD}
Collection Behavior
All deployments are collected concurrently. Individual deployment failures don't stop other collections. Failed collections are retried with exponential backoff (default: 3 attempts).
Validation
# Validate specific deployment
radar-agent validate --deployment enterprise-prod
# Test collection
radar-agent test --deployment session-cache
# Validate all
radar-agent --validate