Redpanda logo

Search the Documentation

Filters
Content Type
Version
Product
Categories
  1. Zafin CTO on the Advantages of Redpanda

    Zafin CTO Shahir Daya shares his experiences in moving from Apache Kafka to Redpanda streaming data, including far simpler ...

    Video
  2. Build a lightning-fast search index using Flink, Elasticsearch, and Redpanda

    Your ticket to robust data pipelines and real-time search apps for seamless streaming, ETL operations, and data indexing

    Blog
  3. How to migrate from Amazon MSK to Redpanda

    Your step-by-step guide on switching to an easy, cost-effective Kafka-compatible alternative

    Blog
  4. Data engineering field guide (part 1)

    Your guide through the wild west of techniques, tools, and technologies for building real-time data pipelines

    Blog
  5. Enterprise Licensing

    You need a valid Enterprise Edition license to use the following enterprise features:

    Doc
  6. Custom Metrics

    You can’t build cool graphs without metrics, and Redpanda Connect emits many. However, occasionally you might want to also emit custom metrics that track data extracted from messages being processed. In this cookbook we’ll explore how to achieve this by configuring Redpanda Connect to pull download stats from Github, DockerHub and Homebrew and emit them as gauges.

    Doc
  7. Create a Snowflake Sink Connector

    You can use the Snowflake Sink connector to ingest and store Redpanda structured data into a Snowflake database for analytics and decision-making.

    Doc
  8. Forced partition recovery

    You can use the Redpanda Admin API to recover a partition that is unavailable and has lost a majority of its replicas. This can occur when the partition replicas have lost Raft consensus, for instance if brokers in a Raft group fail, preventing the group from reaching a majority and electing a new leader.

    Doc
    25.1
  9. Forced partition recovery

    You can use the Redpanda Admin API to recover a partition that is unavailable and has lost a majority of its replicas. This can occur when the partition replicas have lost Raft consensus, for instance if brokers in a Raft group fail, preventing the group from reaching a majority and electing a new leader.

    Doc
    24.3
  10. Forced partition recovery

    You can use the Redpanda Admin API to recover a partition that is unavailable and has lost a majority of its replicas. This can occur when the partition replicas have lost Raft consensus, for instance if brokers in a Raft group fail, preventing the group from reaching a majority and electing a new leader.

    Doc
    24.2
  11. Forced partition recovery

    You can use the Redpanda Admin API to recover a partition that is unavailable and has lost a majority of its replicas. This can occur when the partition replicas have lost Raft consensus, for instance if brokers in a Raft group fail, preventing the group from reaching a majority and electing a new leader.

    Doc
    24.1
  12. Forced partition recovery

    You can use the Redpanda Admin API to recover a partition that is unavailable and has lost a majority of its replicas. This can occur when the partition replicas have lost Raft consensus, for instance if brokers in a Raft group fail, preventing the group from reaching a majority and electing a new leader.

    Doc
    23.3
  13. Programmable Push Filters

    You can use the programmable push filters in Redpanda Console to search for a specific record within a Kafka topic.

    Doc
    24.1
  14. Create a MirrorMaker2 Checkpoint Connector

    You can use the MirrorMaker2 Checkpoint connector to import consumer group offsets from other Kafka clusters.

    Doc
  15. Create an Iceberg Sink Connector

    You can use the Iceberg Sink connector to accomplish the following:

    Doc
  16. Server-Side Schema ID Validation

    You can use server-side schema ID validation for clients using Confluent’s SerDes format that produce to Redpanda brokers. You can also configure Redpanda to inspect and reject records with schema IDs that aren’t valid according to the configured Subject Name strategy and registered with the Schema Registry.

    Doc
    25.1
  17. Server-Side Schema ID Validation

    You can use server-side schema ID validation for clients using Confluent’s SerDes format that produce to Redpanda brokers. You can also configure Redpanda to inspect and reject records with schema IDs that aren’t valid according to the configured Subject Name strategy and registered with the Schema Registry.

    Doc
    24.3
  18. Server-Side Schema ID Validation

    You can use server-side schema ID validation for clients using Confluent’s SerDes format that produce to Redpanda brokers. You can also configure Redpanda to inspect and reject records with schema IDs that aren’t valid according to the configured Subject Name strategy and registered with the Schema Registry.

    Doc
    24.2
  19. Server-Side Schema ID Validation

    You can use server-side schema ID validation for clients using Confluent’s SerDes format that produce to Redpanda brokers. You can also configure Redpanda to inspect and reject records with schema IDs that aren’t valid according to the configured Subject Name strategy and registered with the Schema Registry.

    Doc
    24.1
  20. Server-side Schema ID Validation

    You can use server-side schema ID validation for clients using Confluent’s SerDes format that produce to Redpanda brokers. You can also configure Redpanda to inspect and reject records with schema IDs that aren’t valid according to the configured Subject Name strategy and registered with the Schema Registry.

    Doc
    23.3
  • «
  • ‹
  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • ›
  • »
Image for tracking purposes only
RESOURCES
  • Redpanda.com
  • Redpanda University
  • Kafka vs Redpanda
  • Jepsen report
  • GitHub
COMPANY
  • Contact
  • About us
  • Careers
  • Press
  • Scholarship
QUICK LINKS
  • Pricing
  • Blog
  • Support
  • Privacy policy
  • Terms of use

© 2025 Redpanda Data Inc.