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

chore: consider to start ESE spans in the runtime #2168

Open
franciscolopezsancho opened this issue Jul 1, 2024 · 0 comments
Open

chore: consider to start ESE spans in the runtime #2168

franciscolopezsancho opened this issue Jul 1, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@franciscolopezsancho
Copy link
Contributor

Such Action subscribing to their events have the ESE as the parent.

So instead of having

KalixEndpoint
  | ESE
  | Action

We would have

KalixEndpoint
   | ESE
      | Action

We could set some value in the trace, in the ESE in the runtime side, that we can then read in the SDK in the:

  • ESE and close the span there and then. (not creating a span as we now do. Again, in the SDK side.)
  • Action. Just as it's right now. Creating a new span from the trace coming from the event stored in DB. But with the suggestion above pointing to the ESE and not the Kalix Endpoint.
@franciscolopezsancho franciscolopezsancho added the enhancement New feature or request label Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant