Skip to content

Conversation

@hariso
Copy link
Contributor

@hariso hariso commented Nov 4, 2022

Description

Depends on #732
Fixes #700

Quick checks:

  • I have followed the Code Guidelines.
  • There is no other pull request for the same update/change.
  • I have written unit tests.
  • I have made sure that the PR is of reasonable size and can be easily reviewed.

@hariso hariso changed the title WIP: Stream inspector for connectors WIP: Stream inspector for destinations Nov 10, 2022
@hariso hariso marked this pull request as ready for review November 11, 2022 13:58
@hariso hariso requested a review from a team as a code owner November 11, 2022 13:58
@hariso hariso changed the title WIP: Stream inspector for destinations Stream inspector for destinations Nov 11, 2022
Copy link
Contributor

@lovromazgon lovromazgon left a comment

Choose a reason for hiding this comment

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

I tried it out and it worked, both through a websocket and gRPC, nice work! I think the PR needs some polish but we're definitely on the right track 🙌

Some comments that don't belong anywhere else:

  • Stopping Conduit with an inspector is not possible, Conduit blocks until the client closes the connection.
  • It's possible to start an inspector on a stopped pipeline, we should probably check the status and return an error if that's the case.
  • Similarly it's possible to stop a pipeline and keep an inspector running, I'd also expect the inspector to stop in that case.
  • While testing I was able to process up to 120 records per second (I used https://websocketking.com/), that feels a bit slow given that it's running on the same machine, am I expecting too much?
  • I don't think we mentioned metrics in the design, but I think it would be nice to at least see the number of open inspector sessions on a connector / processor. WDYT? No need to do it in this PR.

@hariso

This comment was marked as resolved.

@hariso

This comment was marked as resolved.

@lovromazgon

This comment was marked as resolved.

@hariso

This comment was marked as resolved.

@lovromazgon

This comment was marked as resolved.

@hariso

This comment was marked as resolved.

@hariso hariso force-pushed the haris/stream-inspector-destination branch from d2c99b2 to 1a94458 Compare November 21, 2022 13:06
@hariso hariso requested a review from lovromazgon November 21, 2022 15:18
Copy link
Contributor

@lovromazgon lovromazgon left a comment

Choose a reason for hiding this comment

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

Mostly just nitpicks, I think this is already looking very nice!

@hariso hariso requested a review from lovromazgon November 28, 2022 13:11
Copy link
Contributor

@lovromazgon lovromazgon left a comment

Choose a reason for hiding this comment

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

LGTM 👏

@hariso hariso merged commit 88ef86b into main Nov 30, 2022
@hariso hariso deleted the haris/stream-inspector-destination branch November 30, 2022 13:29
@hariso hariso mentioned this pull request Nov 30, 2022
4 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Stream Inspector: Destinations

3 participants