-
Notifications
You must be signed in to change notification settings - Fork 744
add statuses API + Go/Python/TypeScript SDK support #9327
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
base: main
Are you sure you want to change the base?
Conversation
ca6b043
to
708d96a
Compare
looking at the example traces, i can't tell– does this approach lose the ability for these traces to parent to a normal trace if users want to display them "normally" ? or is the idea that the CLI prioritizing showing this class of traces over the big ones and then links to both in cloud? |
8d5e2a5
to
39a81b7
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
@vito Please reopen this PR if this should be supported. Thanks |
This comment was marked as outdated.
This comment was marked as outdated.
sdk/elixir/lib/dagger/gen/span.ex
Outdated
|
||
@doc "Start a new instance of the span." | ||
@spec start(t()) :: {:ok, Dagger.Span.t()} | {:error, term()} | ||
def start(%__MODULE__{} = span) do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I don't need to implement OTel span, right?
This comment was marked as outdated.
This comment was marked as outdated.
Signed-off-by: Alex Suraci <alex@dagger.io>
general idea is to keep building on Span primitive as the gateway to context propagation, and to provide a simplified dag.Reveal() API for revealing a bunch of spans without wrapping them (by using a passthrough dummy span). Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
This reverts commit 8b57e44. Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
…pendency management Signed-off-by: Tom Chauveau <tom@dagger.io>
Signed-off-by: Tom Chauveau <tom@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
sometimes this has unreleased APIs Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
* better docs * withActor -> withActorEmoji * add withReceivedMessage (a bit awkward, but when in Rome...) * remove withInternal; we don't really consistently support it yet, unsure if even needed update viztest along the way Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Goals
Global logging? Or do we just do spans?- let's do logging laterLogging to a span?- let's do logging later(internal, encapsulate, encapsulated)reveal/passthroughExpanded vs. collapsed by default?haven't needed this, 'reveal' covers it?Questions/TODOs
Examples
See the
viztest/
changes for examples in Go, Python, and TypeScript.