Redis
Synopsis
Creates a Pub/Sub subscriber that connects to Redis servers and processes messages from specified channels. Supports authentication, TLS encryption, and multiple workers with automatic message handling.
Schema
- id: <numeric>
name: <string>
description: <string>
type: redis
tags: <string[]>
pipelines: <pipeline[]>
status: <boolean>
properties:
address: <string>
port: <numeric>
username: <string>
password: <string>
channel: <string>
reuse: <boolean>
workers: <numeric>
tls:
status: <boolean>
insecure_skip_verify: <boolean>
cert_name: <string>
key_name: <string>
Configuration
Device
| Field | Required | Default | Description |
|---|---|---|---|
id | Y | - | Unique numeric identifier |
name | Y | - | Device name |
description | N | - | Optional description |
type | Y | - | Must be redis |
tags | N | - | Optional tags |
pipelines | N | - | Optional pre-processor pipelines |
status | N | true | Enable/disable the device |
Connection
| Field | Required | Default | Description |
|---|---|---|---|
address | N | "0.0.0.0" | Redis server address |
port | Y | - | Redis server port |
username | N | - | Authentication username |
password | N | - | Authentication password |
channel | Y | - | Channel pattern to subscribe to (supports * wildcard, e.g. logs.*) |
TLS
| Field | Required | Default | Description |
|---|---|---|---|
tls.status | N | false | Enable TLS encryption |
tls.insecure_skip_verify | N | false | Skip TLS certificate verification |
tls.cert_name | Y* | - | TLS certificate file name |
tls.key_name | Y* | - | TLS private key file name |
* = Conditionally required when tls.status is true.
The TLS certificate and key files must be placed in the service root directory.
Performance
| Field | Required | Default | Description |
|---|---|---|---|
reuse | N | false | Enable multi-worker mode |
workers | N | 4 | Number of worker processes when reuse enabled (capped at the number of available CPU cores) |
Examples
Basic
Creating a simple Redis Pub/Sub subscriber on a single channel... | |
Secure
Connecting with authentication and TLS encryption... | |
High-Volume
Multi-worker mode for high-throughput consumption... | |
Pattern Subscription
Pattern-based subscription using a wildcard channel... | |
Redis channel patterns support the * wildcard character for matching multiple channels.
Pipelines
Applying custom processing to messages... | |
Pipelines are processed sequentially, and can modify or drop messages before ingestion.