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

track stable function call hash + more attrs #7321

Draft
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

vito
Copy link
Contributor

@vito vito commented May 8, 2024

  • moved telemetry/graphql.go to core/telemetry.go so it can integrate with Query to get necessary module metadata

  • dagger.io/dag.digest.stable is a Call's 'stable digest'. This digest can be used to compare performance of the same Call across different inputs over time. This calculation involves simply recursing through a call and removing any embedded Calls passed as arguments.

  • dagger.io/dag.caller.type indicates whether the span comes from a direct user call, a call from a module, or an internal call. We can use this to identify the top-level calls for browsing (type == direct).

  • various attributes (name, ref, digest) for identifying a Call's module have been added, though they might be of limited utility at the moment (see large TODO comment).

  • All these attribute names are a bit of a mess, this might be a good time to bikeshed them

vito added 4 commits May 9, 2024 11:21
* dagger.io/dag.digest.stable is a Call's 'stable digest'. This digest
  can be used to compare performance of the same Call across different
  inputs over time. This calculation involves simply recursing through a
  call and removing any embedded Calls passed as arguments.
* dagger.io/dag.caller.type indicates whether the span comes from a
  direct user call, a call from a module, or an internal call. We can
  use this to identify the top-level calls for browsing (type ==
  direct).
* various attributes for identifying a Call's module have been added,
  though they might be of limited utility at the moment (see large TODO
  comment).

Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
Signed-off-by: Alex Suraci <alex@dagger.io>
previously we would always emit all the digests needed by an object,
which made it impossible to tell (without heuristics) which ones were
actually "new" effects installed by the individual call

Signed-off-by: Alex Suraci <alex@dagger.io>
Copy link
Contributor

This PR is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days.

@github-actions github-actions bot added the stale label May 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant