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

Expose trace information to users #76

Closed
Tracked by #38
slinkydeveloper opened this issue Mar 20, 2023 · 1 comment · Fixed by #296
Closed
Tracked by #38

Expose trace information to users #76

slinkydeveloper opened this issue Mar 20, 2023 · 1 comment · Fixed by #296
Labels
enhancement New feature or request

Comments

@slinkydeveloper
Copy link
Contributor

slinkydeveloper commented Mar 20, 2023

We should find a way to expose the span context of the current invocation span, to allow users to create child spans from the current invocation, e.g. to include trace info when invoking another http service.

@slinkydeveloper slinkydeveloper added the enhancement New feature or request label Mar 20, 2023
slinkydeveloper added a commit that referenced this issue Mar 22, 2024
….29b28f98

29b28f98 Modify Input/Output schema in deployment_manifest_schema.json (#80)
26d91e69 Replace protocol Empty message with custom one, so we remove the dependency on protobuf built-in messages (#79)
61ae44b2 Update documentation on error codes (#77)
576a1b26 Add HandlerType. Fix #1092 (#76)
0624d092 Payload schema for input and output. This provides basic format awareness. (#74)

git-subtree-dir: sdk-core/src/main/service-protocol
git-subtree-split: 29b28f9867734bc01dd47c4666d9d56c90b626f5
slinkydeveloper added a commit that referenced this issue Mar 22, 2024
* Squashed 'sdk-core/src/main/service-protocol/' changes from 4378d559..29b28f98

29b28f98 Modify Input/Output schema in deployment_manifest_schema.json (#80)
26d91e69 Replace protocol Empty message with custom one, so we remove the dependency on protobuf built-in messages (#79)
61ae44b2 Update documentation on error codes (#77)
576a1b26 Add HandlerType. Fix #1092 (#76)
0624d092 Payload schema for input and output. This provides basic format awareness. (#74)

git-subtree-dir: sdk-core/src/main/service-protocol
git-subtree-split: 29b28f9867734bc01dd47c4666d9d56c90b626f5

* Changes due to the protocol update
@slinkydeveloper
Copy link
Contributor Author

see restatedev/restate#1279, we need to propagate the otel context

slinkydeveloper added a commit that referenced this issue Apr 16, 2024
….98bd326c

98bd326c Entry names + specify the entry that caused the failure in ErrorMessage (#86)
c47e65b0 Describe x-restate-user-agent (#85)
d43de04c Describe side effects in protocol (#84)
29b28f98 Modify Input/Output schema in deployment_manifest_schema.json (#80)
26d91e69 Replace protocol Empty message with custom one, so we remove the dependency on protobuf built-in messages (#79)
61ae44b2 Update documentation on error codes (#77)
576a1b26 Add HandlerType. Fix #1092 (#76)
0624d092 Payload schema for input and output. This provides basic format awareness. (#74)

git-subtree-dir: sdk-core/src/main/service-protocol
git-subtree-split: 98bd326c23f060d962821bca982bbb881e32c540
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

Successfully merging a pull request may close this issue.

1 participant