docs: add Redis Sentinel configuration documentation

[Steffen911]

Summary

This PR adds comprehensive documentation for Redis Sentinel mode support, following the implementation in langfuse/langfuse#9851.

Changes

Updated Files

pages/self-hosting/deployment/infrastructure/cache.mdx

• Added 5 new Redis Sentinel environment variables to the configuration table
• Added new "Redis Sentinel Mode" section with:
  • Overview of Sentinel mode benefits (high availability without cluster complexity)
  • Configuration examples for self-hosted and TLS setups
  • Best practices and warnings for production deployments
  • Note about mutual exclusivity with cluster mode

pages/self-hosting/configuration/index.mdx

• Added 5 new Redis Sentinel environment variables to the reference table:
  • REDIS_SENTINEL_ENABLED
  • REDIS_SENTINEL_NODES
  • REDIS_SENTINEL_MASTER_NAME
  • REDIS_SENTINEL_USERNAME
  • REDIS_SENTINEL_PASSWORD

Key Documentation Points

• Redis Sentinel provides high availability with automatic failover
• Sentinel and Cluster modes are mutually exclusive
• Minimum 3 Sentinel instances recommended for production
• TLS configuration applies to both Sentinel and Redis connections
• maxmemory-policy=noeviction must be set on master and replicas

Related

• Implementation PR: feat(redis): add support of the sentinel mode for Redis client langfuse#9851
• Discussion: https://github.com/orgs/langfuse/discussions/6837

🤖 Generated with Claude Code

---

Important

Adds documentation for Redis Sentinel configuration, including environment variables and best practices, to cache.mdx and index.mdx.

• Documentation:
  • Adds Redis Sentinel configuration documentation to cache.mdx.
  • Adds 5 Redis Sentinel environment variables to index.mdx and cache.mdx.
• Environment Variables:
  • REDIS_SENTINEL_ENABLED, REDIS_SENTINEL_NODES, REDIS_SENTINEL_MASTER_NAME, REDIS_SENTINEL_USERNAME, REDIS_SENTINEL_PASSWORD added.
• Best Practices:
  • Redis Sentinel provides high availability with automatic failover.
  • Sentinel and Cluster modes are mutually exclusive.
  • Minimum 3 Sentinel instances recommended for production.
  • TLS configuration applies to both Sentinel and Redis connections.
  • maxmemory-policy=noeviction must be set on master and replicas.

^{This description was created by for 8c7633a. You can customize this summary. It will automatically update as commits are pushed.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
langfuse-docs	Ready	Preview	Nov 7, 2025 9:52am

[github-actions]

📦 Next.js Bundle Analysis for langfuse-docs

This analysis was generated by the Next.js Bundle Analysis action. 🤖

One Page Changed Size

The following page changed size from the code in this PR compared to its base branch:

Page	Size (compressed)	First Load	% of Budget (350 KB)
/self-hosting/deployment/infrastructure/cache	58.3 KB	454.44 KB	129.84% (🟡 +0.19%)

Details

Only the gzipped size is provided here based on an expert tip.

First Load is the size of the global bundle plus the bundle for the individual page. If a user were to show up to your website and land on a given page, the first load size represents the amount of javascript that user would need to download. If next/link is used, subsequent page loads would only need to download that page's bundle (the number in the "Size" column), since the global bundle has already been downloaded.

Any third party scripts you have added directly to your app using the <script> tag are not accounted for in this analysis

The "Budget %" column shows what percentage of your performance budget the First Load total takes up. For example, if your budget was 100kb, and a given page's first load size was 10kb, it would be 10% of your budget. You can also see how much this has increased or decreased compared to the base branch of your PR. If this percentage has increased by 20% or more, there will be a red status indicator applied, indicating that special attention should be given to this. If you see "+/- <0.01%" it means that there was a change in bundle size, but it is a trivial enough amount that it can be ignored.