Skip to main content
Destinations refer to data connectors we will send data to. On this page you can create new connectors or view the status of existing ones. Functionality
  • Create
  • View existing Destinations & Quick Actions
  • Create & Edit Authentication
  • Settings
  • Status
  • Config History

​
View Existing Destinations

  • Shows types, quantity of topics latency
  • Able to search and filter the list

​
Quick Actions

  • View
  • Stop/Resume
  • Reset
Resetting Resetting a Destination will clear all offsets and replay up to 7 days of data. This may cause duplicate events in downstream systems. It may also trigger consumer lag alerts until the data backlog is cleared.This is a destructive action and should be used with caution. You will be prompted to confirm this action.
  • Clone
  • Logs
  • Delete

​
Create & Edit Authentication

​
Settings

Varies per connector but you will find values to configure such as metadata to create

​
Status

  • View headline statistics such as Latency
  • View volume, events retries and snapshot status per table/topic
  • Trigger a new snapshot/backfill per connecor or table/topics

​
Config History

The Config History tab provides a complete timeline of all configuration changes made to your connector. This feature helps you track changes over time, understand their impact, and troubleshoot issues. What’s Tracked:
  • Kafka Connect configuration changes that affect data flow
  • Changes made during connector creation and edits
  • Both successful and failed configuration updates
  • Note: Metadata updates (name, tags, description) are not included
Key Features:
  • Timeline View - Chronological list of all configuration changes with timestamps
  • Status Indicators - Visual indicators showing successful (green) and failed (red) updates
  • AI-Generated Summaries - Streamkap AI analyzes each change and provides:
    • A clear explanation of what was modified
    • Potential impact on your data pipeline
    • Relevant warnings about performance or data flow changes
  • Sync Delay Notice - Recent changes may take a few minutes to appear as the system syncs
Example Use Cases:
  • Investigate when a configuration change caused an issue
  • Review the history of schema or table inclusion changes
  • Understand how settings like snapshot parallelism or table lists have evolved
  • Document configuration changes for compliance or audit purposes

​
Quick Actions

  • Stop/Resume
  • Clone
  • Delete