Redis

This article outlines the integration with the Redis connector, enabling streamlined metadata management through features such as crawling, querying, and data preview. It also ensures secure authentication via Credential Manager.

Overview

Connector Details

Connector Category

NoSQL

OvalEdge Release Supported

Release8.1

Connectivity

[How the connection is established with Redis]

Redis Protocol over TCP (TLS Optional)

Connector Features

Feature
Availability

Crawling

Delta Crawling

Profiling

Query Sheet

Data Preview

Auto Lineage

Manual Lineage

Secure Authentication via Credential Manager

Data Quality

DAM (Data Access Management)

Bridge

Metadata Mapping

The following objects are crawled from Redis and mapped to the corresponding UI assets.

Redis Object
Redis Attribute
OvalEdge Attribute
OvalEdge Category
OvalEdge Type

All Keys

Key name

Key identifier

Table / entity

Entity

String Keys

Key name

Key identifier

Table / entity

Entity

Hash Keys

Key name

Key identifier

Table / entity

Entity

List Keys

Key name

Key identifier

Table / entity

Entity

Set Keys

Key name

Key identifier

Table / entity

Entity

Sorted Set Keys

Key name

Key identifier

Table / entity

Entity

JSON Keys

Key name

Key identifier

Table / entity

Entity

Key Fields

Key attributes (Key name, Type, TTL & Value preview)

Column list for key preview

Column

Column

Set up a Connection

Prerequisites

The following are the prerequisites to establish a connection:

Whitelisting Ports

Ensure outbound connectivity from the OvalEdge application environment is allowed to the Redis server over the required TCP port:

• Default without TLS: `6379`

• Common with TLS: `6380`

The exact port depends on how your Redis endpoint is configured.

Service Account User Permissions

circle-exclamation
circle-info

👨‍💻 Who can provide these permissions? These permissions are typically granted by the Redis administrator, as users may not have the required access to assign them independently.

Operation
Objects
Access Permission

Connection Validation

Redis Server

Ability to authenticate (if configured) and execute `PING`

Crawling Database Keys

Redis database keys

Ability to scan keys with `SCAN` and read metadata such as `TYPE` and TTL

Crawling Key Preview Fields

Redis keys of supported types

Ability to read key contents required for preview (e.g. `GET`, `HGETALL`, `LRANGE`, `SMEMBERS`, `ZRANGE`, JSON commands depending on key type)

Query Sheet / Data Preview

Selected keys

Ability to read the selected key values for rendering a preview

Connection Configuration Steps

circle-exclamation
  1. Log into OvalEdge, go to Administration > Connectors, click + (New Connector), search for Redis, and complete the required parameters.

circle-info

Fields marked with an asterisk (*) are mandatory for establishing a connection.

Field Name
Description

Connector Type

By default, "Redis" is displayed as the selected connector type.

Credential Manager*

Select the desired credentials manager from the drop-down list. Relevant parameters will be displayed based on your selection.

Supported Credential Managers:

  • OE Credential Manager

  • AWS Secrets Manager

  • HashiCorp Vault

  • Azure Key Vault

Connector Name*

Enter a unique name for the Redis connection

(Example: "Redis_Prod").

Connector Description

Enter a brief description of the connector.

Host*

Enter the Redis host name or IP address. For Redis Cloud, use the endpoint host.

Port

By default, the port number for the Redis, "6379" is auto-populated or 6380 for TLS.

Username

Enter the Redis username if required. Leave blank to use the default user.

Database Password*

Enter the password for the Redis user.

Database

Enter the Redis database index. The default value is 0.

Timeout (ms)

Enter the connection timeout in milliseconds for validation.

Example: 5000.

TLS Enabled

Enable TLS or SSL when connecting to Redis. Use true for Redis Cloud endpoints.

  1. After entering all connection details, the following actions can be performed:

    1. Click Validate to verify the connection.

    2. Click Save to store the connection for future use.

    3. Click Save & Configure to apply additional settings before saving.

  2. The saved connection will appear on the Connectors home page.

Manage Connector Operations

Crawl/Profile

circle-info

To perform crawl operations, users must be assigned the Integration Admin role.

For Redis, containers represent logical Redis database indexes (for example `0` by default).

The Crawl/Profile button allows users to select one or more schemas for crawling.

  1. Navigate to the Connectors page and click Crawl/Profile.

  2. Select the schemas to crawl.

  3. The Crawl option is selected by default.

  4. Click Run to collect metadata from the connected source and load it into the OvalEdge Data Catalog.

  5. After a successful crawl, the information appears in the OvalEdge Data Catalog.

The Schedule checkbox allows automated crawling at defined intervals, from a minute to a year.

  1. Click the Schedule checkbox to enable the Select Period drop-down.

  2. Select a time period for the operation from the drop-down menu.

  3. Click Schedule to initiate metadata collection from the connected source.

  4. The system will automatically execute the crawl operation at the scheduled time.

Other Operations

The Connectors page in OvalEdge provides a centralized view of all configured connectors, including their health status.

Managing connectors includes:

  • Connectors Health: Displays the current status of each connector using a green icon for active connections and a red icon for inactive connections, helping to monitor the connectivity with data sources.

  • Viewing: Click the Eye icon next to the connector name to view connector details, including databases, tables, columns, and codes.

Nine Dots Menu Options:

To view, edit, validate, configure, or delete connectors, click on the Nine Dots menu.

  • Edit Connector: Update and revalidate the data source.

  • Validate Connector: Check the connection's integrity.

  • Settings: Modify connector settings.

    • Crawler: Configure data extraction.

    • Query Policies: Define query execution rules based on roles.

    • Access Instructions: Add notes on how data can be accessed.

    • Business Glossary Settings: Manage term associations at the connector level.

    • Others: Configure notification recipients for metadata changes

  • Delete Connector: Remove a connector with confirmation.

Connectivity Troubleshooting

If incorrect parameters are entered, error messages may appear. Ensure all inputs are accurate to resolve these issues. If issues persist, contact the assigned support team.

S.No.
Error Message (s)
Error Description & Resolution

1

Invalid connection config.

Error Description:

  • Required connection settings were missing when validation ran.

Resolution:

  • Open the connector settings.

  • Enter all required fields such as Host and Database Password.

  • Validate the connection again.

2

Redis host is required.

Error Description:

  • No Redis host was provided.

Resolution:

  • Enter the Host value.

  • Use the endpoint host for Redis Cloud.

  • Run validation again.

3

Redis API account key is required.

Error Description:

  • No API account key/credentials were provided.

Resolution:

  • Enter the Database Password.

  • Verify the credentials are correct.

  • Validate the connection again.

4

Connection failed: (message from driver/server)

Error Description:

  • Redis authentication or network connectivity failed during validation.

Resolution:

  • Verify host, port, and TLS settings.

  • Check credentials and firewall rules.

  • Retry the connection.

5

entityId (Redis key) is required.

Error Description:

  • A data preview/query request was submitted without a selected Redis key.

Resolution:

  • Select a Redis key from the data catalog.

  • Use a key pattern filter if needed.

  • Run query or preview again.

6

Key not found or could not be fetched

Error Description:

  • The selected key cannot be accessed or was deleted/expired since crawling.

Resolution:

  • Run crawl again to refresh keys.

  • Select a valid key.

  • Verify read access for the key.


Copyright © 2026, OvalEdge LLC, Peachtree Corners GA USA

Last updated

Was this helpful?