Skip to content

RS 8.2.x release docs#3640

Open
rrelledge wants to merge 40 commits into
release-rs-8.2.0from
DOC-6645
Open

RS 8.2.x release docs#3640
rrelledge wants to merge 40 commits into
release-rs-8.2.0from
DOC-6645

Conversation

@rrelledge

@rrelledge rrelledge commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

These are drafts and this PR is still a work in progress.


Note

Low Risk
Documentation-only changes with no runtime impact; reviewers should still validate breaking-change and security guidance (auditing, REST auth, module upload defaults) before GA.

Overview
Adds Redis Software 8.2.x documentation: draft 8.2.0 release notes (highlights, breaking changes, deprecations, CVE lists), an 8.2.x release index, and updates to product lifecycle, supported platforms, upgrade paths, and bundled DB versions (8.2.0 row, default Redis 8.6).

Expands operational and API coverage for 8.2 capabilities: per-database audit_settings (connection + CRUD auditing, filters, metrics) with a major rewrite of audit-events; resources on roles for db_member/db_viewer scoping; new disable basic authentication guide and control_plane_basic_authentication / allow_modules_upload cluster fields; gradual_sync_policy on databases; richer database availability / bdb_unavailable_* error documentation; and a new RediSearch v2 Prometheus metric redis_server_search_total_coord_dispatch_time_ms.

Reviewed by Cursor Bugbot for commit 8f889a5. Bugbot is set up for automated code reviews on this repo. Configure here.

@rrelledge
rrelledge requested a review from yoavredis July 15, 2026 02:24
@rrelledge rrelledge self-assigned this Jul 15, 2026
@rrelledge rrelledge added do not merge yet rs Redis Software labels Jul 15, 2026
@CLAassistant

CLAassistant commented Jul 15, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

DOC-6645

@github-actions

github-actions Bot commented Jul 15, 2026

Copy link
Copy Markdown
Contributor

Staging links:
https://redis.io/docs/staging/DOC-6645/integrate/prometheus-with-redis-enterprise/prometheus-metrics-definitions
https://redis.io/docs/staging/DOC-6645/operate/rs/7.22/installing-upgrading/product-lifecycle
https://redis.io/docs/staging/DOC-6645/operate/rs/7.22/installing-upgrading/upgrading/upgrade-cluster
https://redis.io/docs/staging/DOC-6645/operate/rs/7.22/references/metrics/prometheus-metrics-v2
https://redis.io/docs/staging/DOC-6645/operate/rs/7.22/references/upgrade-paths
https://redis.io/docs/staging/DOC-6645/operate/rs/7.4/installing-upgrading/product-lifecycle
https://redis.io/docs/staging/DOC-6645/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster
https://redis.io/docs/staging/DOC-6645/operate/rs/7.4/references/upgrade-paths
https://redis.io/docs/staging/DOC-6645/operate/rs/7.8/installing-upgrading/product-lifecycle
https://redis.io/docs/staging/DOC-6645/operate/rs/7.8/installing-upgrading/upgrading/upgrade-cluster
https://redis.io/docs/staging/DOC-6645/operate/rs/7.8/references/upgrade-paths
https://redis.io/docs/staging/DOC-6645/operate/rs/installing-upgrading/product-lifecycle
https://redis.io/docs/staging/DOC-6645/operate/rs/installing-upgrading/product-lifecycle/
https://redis.io/docs/staging/DOC-6645/operate/rs/installing-upgrading/upgrading/upgrade-cluster
https://redis.io/docs/staging/DOC-6645/operate/rs/monitoring/db-availability/
https://redis.io/docs/staging/DOC-6645/operate/rs/monitoring/metrics_stream_engine/prometheus-metrics-v2
https://redis.io/docs/staging/DOC-6645/operate/rs/references/metrics/prometheus-metrics-v2
https://redis.io/docs/staging/DOC-6645/operate/rs/references/rest-api/objects/bdb/
https://redis.io/docs/staging/DOC-6645/operate/rs/references/rest-api/objects/bdb/audit_settings/
https://redis.io/docs/staging/DOC-6645/operate/rs/references/rest-api/objects/cluster/
https://redis.io/docs/staging/DOC-6645/operate/rs/references/rest-api/objects/role/
https://redis.io/docs/staging/DOC-6645/operate/rs/references/rest-api/requests/bdbs/availability/
https://redis.io/docs/staging/DOC-6645/operate/rs/references/upgrade-paths
https://redis.io/docs/staging/DOC-6645/operate/rs/release-notes/rs-8-2-releases/
https://redis.io/docs/staging/DOC-6645/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-tba/
https://redis.io/docs/staging/DOC-6645/operate/rs/security/access-control/create-cluster-roles/
https://redis.io/docs/staging/DOC-6645/operate/rs/security/access-control/disable-basic-authentication/
https://redis.io/docs/staging/DOC-6645/operate/rs/security/audit-events/


| Port | Process name | Usage |
|------|--------------|-------|
| 3357 | reconciliation_tree_grpc | Internal communication |

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Duplicate port 3357 table

Low Severity

The reserved-ports section lists port 3357 (reconciliation_tree_grpc) twice in back-to-back identical markdown tables, which reads like an accidental copy-paste in new 8.2.x release notes.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 462c3aa. Configure here.

Comment thread content/operate/rs/release-notes/rs-8-2-releases/rs-8-2-0-tba.md

- _audit\_reconnect\_max\_attempts_ defines the maximum number of attempts to reconnect. Default is 0. (infinite)
- _audit\_reconnect\_max\_attempts_ sets the maximum number of reconnection attempts. Default is 0 (infinite).

@yoavredis yoavredis Jul 19, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missing a description for the "audit_queue_max_bytes" field:
Maximum amount of audit data that can wait in the outgoing audit queue. When the queue has no remaining capacity, new audit records can be dropped.

Comment thread content/operate/rs/security/audit-events.md Outdated
Comment thread content/operate/rs/security/audit-events.md
{{< /multitabs >}}

The socket file and path must be accessible by the user and group running Redis Software.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a section for "Audit modes":

Auditing is configured independently for each database with audit_settings.audit_mode.

Maybe add a 2-column table for "value" and "Description":

disabled: Disables connection, authentication, and command audit records for the database. This is the default mode.

connection: Audits database connection, disconnection, and authentication events only.

connection_and_crud: Audits connection and authentication events and individual database commands.

Command auditing cannot be enabled without connection auditing. The connection_and_crud mode always includes the connection and authentication events generated by connection mode.

| `10` | The command failed. The `error` field contains the returned error message. |

## Monitor auditing metrics

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's incorporate the below content in the metrics section (or any other location you think is better...):

Audit delivery during sink interruptions

If the audit destination becomes unavailable, Redis Software continues serving database traffic and attempts to reconnect according to audit_reconnect_interval and audit_reconnect_max_attempts.

Audit records can wait in the outgoing audit queue while delivery is unavailable. The amount of queued data is limited by audit_queue_max_bytes. Redis Software can discard audit records in the following situations:

  • The outgoing queue has reached its configured capacity.
  • A single audit record exceeds the supported queue or record-size limit.
  • No active connection to the audit destination is available when the record must be delivered.
  • An attempt to send the record fails.
  • Queuing is disabled or unavailable.

Audit delivery is best effort. Database operations are not delayed or rejected because audit records cannot be delivered.

Use the following metrics to identify delivery problems:

  • audit_sink_pending_bytes indicates how much audit data is currently waiting to be sent.
  • audit_sink_dropped_messages and audit_sink_dropped_bytes indicate total audit data discarded before delivery.
  • audit_sink_dropped_queue_full_messages indicates that the outgoing queue did not have enough capacity.
  • audit_sink_dropped_record_too_large_messages indicates that an individual audit record exceeded the permitted size.
  • audit_sink_reconnect_attempts_exhausted indicates that the configured reconnect-attempt limit was reached.

{{</note>}}

When a tracked event occurs, Redis Software sends a notification over TCP to the address and port you configure when you enable auditing. Notifications arrive in near real time for an external listener to consume, such as a TCP listener, third-party service, or related utility.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

State the tool-agnostic integration model explicitly. The page lists example listeners, but does not clearly say that Redis Software does not require or enforce any particular SIEM/DAM vendor.

Comment thread content/operate/rs/references/rest-api/objects/bdb/_index.md Outdated

@yoavredis yoavredis left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kaitlynmichael I've added comments for auditing, 10x

Comment thread content/operate/rs/security/audit-events.md

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

Fix All in Cursor

❌ 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 c8c9162. Configure here.


Make sure the following ports are open before upgrading Redis Software.

The following port was added as a reserved port in Redis Software version 8.0.18; however, it is optional instead of reserved in Redis Software version 8.0.20-44:

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wrong optional-port release version

Medium Severity

The 8.2.x release index states port 3357 became optional in version 8.0.20-44, while the 8.2.0 release notes in the same PR say it became optional in “this release” (8.2). Those statements cannot both be accurate for the same change.

Additional Locations (1)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit c8c9162. Configure here.

@kaitlynmichael
kaitlynmichael requested a review from yoavredis July 20, 2026 14:50
@kaitlynmichael
kaitlynmichael changed the base branch from main to release-rs-8.2.0 July 20, 2026 14:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rs Redis Software

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants