Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

adding Kafka Destination docs #6280

Merged
merged 7 commits into from
Mar 27, 2024
Merged

adding Kafka Destination docs #6280

merged 7 commits into from
Mar 27, 2024

Conversation

joe-ayoub-segment
Copy link
Contributor

Adding docs for new Kafka Destination

Proposed changes

Adding docs for new Kafka Destination
Destination slug is: actions-kafka

Merge timing

Please publish but keep it hidden from customers for now until the Destination is in Public Beta.

Related issues (optional)

@joe-ayoub-segment joe-ayoub-segment requested a review from a team as a code owner March 25, 2024 14:20
@joe-ayoub-segment joe-ayoub-segment requested review from forstisabella and removed request for a team March 25, 2024 14:20
@@ -0,0 +1,71 @@
---
title: Kafka Destination
Copy link
Contributor

Choose a reason for hiding this comment

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

hi @joe-ayoub-segment - do you know the ID for this destination?

Copy link
Contributor

Choose a reason for hiding this comment

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

also - if the slug is actions-kafka, you'll need to either rename the file or add a redirect to the frontmatter so that the app/segment.com site can correctly point to these docs

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hi @forstisabella the ID is 65dde5755698cb0dab09b489

I'll rename the folder to actions-kafka

Copy link
Contributor

Choose a reason for hiding this comment

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

sweet! thanks. It looks good to me, but I'm going to hold off on deploying this today, as I haven't figured out how to keep the ordered lists from resetting under each heading (and the Jira ticket has a docs required date of March 29th, so I've got some time to work through this).

Copy link
Contributor

@forstisabella forstisabella left a comment

Choose a reason for hiding this comment

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

A few changes and we'll be good to go! I'll take a deeper look at the numbering, as I don't think it'll reset if you add a header between lists

@@ -0,0 +1,71 @@
---
title: Kafka Destination
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
title: Kafka Destination
title: Kafka Destination
beta: true
hidden: true
id:


[Kafka](https://kafka.apache.org/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank”} provides a highly scalable and fault-tolerant messaging system that enables real-time data processing and stream processing at scale. When integrated with Segment, Kafka serves as a powerful backbone for managing and processing event data collected by Segment, allowing businesses to efficiently ingest, route, and analyze data across various applications and systems in real time.

This destination is maintained by Segment.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This destination is maintained by Segment.
This destination is maintained by Segment. For any issues with the destination, [contact the Segment Support team](mailto:friends@segment.com).

Comment on lines 15 to 16
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka"
2. Select the "Kafka" tile and click **Add Destination**
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka"
2. Select the "Kafka" tile and click **Add Destination**
1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka".
2. Select the "Kafka" tile and click **Add Destination**.


1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka"
2. Select the "Kafka" tile and click **Add Destination**
3. Select an existing Source to connect to Kafka.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
3. Select an existing Source to connect to Kafka.
3. Select an existing source to connect to Kafka.

1. From your workspace's [Destination catalog page](https://app.segment.com/goto-my-workspace/destinations/catalog){:target="_blank”} search for "Kafka"
2. Select the "Kafka" tile and click **Add Destination**
3. Select an existing Source to connect to Kafka.
4. Give your Kafka Destination a name.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
4. Give your Kafka Destination a name.
4. Enter a name for your Kafka destination.

For **AWS**: Provide values for **AWS Access Key ID** and **AWS Secret Key** fields, and optionally for the **AWS Authorization Identity** field.
For **Client Certificate** you will need to provide values for the **SSL Client Key** and **SSL Client Certificate** Settings fields.
7. Optionally populate the **SSL Certificate Authority** field.
8. Save your changes before proceeding to the next step.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
8. Save your changes before proceeding to the next step.
8. Save your changes and proceed to Configure the Send Action .

For **Plain** or **SCRAM-SHA-256 / 512**: provide values for **Username** and **Password** fields.
For **AWS**: Provide values for **AWS Access Key ID** and **AWS Secret Key** fields, and optionally for the **AWS Authorization Identity** field.
For **Client Certificate** you will need to provide values for the **SSL Client Key** and **SSL Client Certificate** Settings fields.
7. Optionally populate the **SSL Certificate Authority** field.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
7. Optionally populate the **SSL Certificate Authority** field.
7. Populate the **SSL Certificate Authority** field, if necessary.

Comment on lines 26 to 28
For **Plain** or **SCRAM-SHA-256 / 512**: provide values for **Username** and **Password** fields.
For **AWS**: Provide values for **AWS Access Key ID** and **AWS Secret Key** fields, and optionally for the **AWS Authorization Identity** field.
For **Client Certificate** you will need to provide values for the **SSL Client Key** and **SSL Client Certificate** Settings fields.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
For **Plain** or **SCRAM-SHA-256 / 512**: provide values for **Username** and **Password** fields.
For **AWS**: Provide values for **AWS Access Key ID** and **AWS Secret Key** fields, and optionally for the **AWS Authorization Identity** field.
For **Client Certificate** you will need to provide values for the **SSL Client Key** and **SSL Client Certificate** Settings fields.
- **Plain** or **SCRAM-SHA-256 / 512** authentication: provide values for **Username** and **Password** fields.
- **AWS** authentication: Provide values for **AWS Access Key ID** and **AWS Secret Key** fields, and optionally for the **AWS Authorization Identity** field.
- **Client Certificate** authentication: provide values for the **SSL Client Key** and **SSL Client Certificate** fields.

Authentication and Encryption settings for Kafka depend on the way your cluster is configured. You may need the assistance of someone technical to provide values for the following configuration Settings:

5. On the Settings tab, provide values for the **Client ID**, **Brokers** and **Authentication Mechanism** Setting fields.
6. Populate fields for your selected **Authentication Mechanism**:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
6. Populate fields for your selected **Authentication Mechanism**:
6. Populate fields for your selected authentication mechanism:


### Configure the Kafka Destination

Authentication and Encryption settings for Kafka depend on the way your cluster is configured. You may need the assistance of someone technical to provide values for the following configuration Settings:
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Authentication and Encryption settings for Kafka depend on the way your cluster is configured. You may need the assistance of someone technical to provide values for the following configuration Settings:
The way you configured your cluster informs the authentication and encryption settings you'll need to set up for Kafka. You may need the assistance of someone technical to provide values for the following configuration Settings:

@forstisabella forstisabella added the new-integration Added a new source or destination label Mar 25, 2024
@joe-ayoub-segment
Copy link
Contributor Author

hi @forstisabella I've applied all the suggestions.

@forstisabella forstisabella self-requested a review March 26, 2024 15:48
@forstisabella forstisabella self-requested a review March 26, 2024 17:09
Copy link
Contributor

@forstisabella forstisabella left a comment

Choose a reason for hiding this comment

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

lgtm - waiting to merge until I can fix the ordering under the different subheadings in the procedure

@forstisabella forstisabella merged commit 9758233 into develop Mar 27, 2024
4 checks passed
@forstisabella forstisabella deleted the kafka branch March 27, 2024 22:15
Copy link
Contributor

Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new-integration Added a new source or destination
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants