feat: retrieve operation body from gqlmetrics instead of traces #2235
Conversation
WalkthroughAdds an OperationContentAttributes flag to control emitting GraphQL operation original/normalized body content into traces; wires the flag through config, trace config, router, GraphQL prehandler, and tests; introduces new OTEL attribute keys; updates Studio to fetch/display operation content; adds an OTEL processor to delete those attributes; consolidates a null/empty check. Changes
Estimated code review effort🎯 4 (Complex) | ⏱️ ~60 minutes Possibly related PRs
Pre-merge checks and finishing touches❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✨ Finishing touches
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro 📒 Files selected for processing (15)
🚧 Files skipped from review as they are similar to previous changes (9)
🧰 Additional context used🧠 Learnings (2)📓 Common learnings📚 Learning: 2025-10-01T20:39:16.113ZApplied to files:
🧬 Code graph analysis (4)router/pkg/trace/config.go (1)
router/core/graphql_prehandler.go (1)
router-tests/telemetry/telemetry_test.go (4)
studio/src/components/analytics/trace-details.tsx (6)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (6)
🔇 Additional comments (14)
Comment |
Router image scan passed✅ No security vulnerabilities found in image: |
endigma
force-pushed
the
jesse/eng-7530-different-queries-different-spans
branch
from
71b2aa1 to
f62a624
Compare
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
endigma
force-pushed
the
jesse/eng-7530-different-queries-different-spans
branch
from
b0273e8 to
ba3d95e
Compare
endigma
requested review from
JivusAyrus,
Noroth,
StarpTech,
devsergiy,
jensneuse,
thisisnithin and
wilsonrivera
as code owners
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (2)
router/core/graphql_prehandler.go (2)
529-548: Missing default in method switch allows unsupported HTTP methods to slip throughRequests with methods other than GET/POST won’t be unmarshaled and may fail later in confusing ways. Return 405 early for unsupported methods.
Apply this diff:
switch req.Method { case http.MethodGet: if err := operationKit.UnmarshalOperationFromURL(req.URL); err != nil { return &httpGraphqlError{ message: fmt.Sprintf("invalid GET request: %s", err), statusCode: http.StatusBadRequest, } } case http.MethodPost: if err := operationKit.UnmarshalOperationFromBody(httpOperation.body); err != nil { return &httpGraphqlError{ message: fmt.Sprintf("invalid request body: %s", err), statusCode: http.StatusBadRequest, } } // If we have files, we need to set them on the parsed operation if len(httpOperation.files) > 0 { requestContext.operation.files = httpOperation.files } +default: + return &httpGraphqlError{ + message: fmt.Sprintf("method %s not allowed, only GET and POST are supported", req.Method), + statusCode: http.StatusMethodNotAllowed, + } }
910-914: Bug: setting attributes after span.End()
engineNormalizeSpan.SetAttributes(...)is called afterengineNormalizeSpan.End(), which is a no-op or error in most SDKs. Move attribute setting beforeEnd()(or drop it as it’s already set on the “Load Persisted Operation” span).Apply this diff:
- engineNormalizeSpan.End() - - if operationKit.parsedOperation.IsPersistedOperation { - engineNormalizeSpan.SetAttributes(otel.WgEnginePersistedOperationCacheHit.Bool(operationKit.parsedOperation.PersistedOperationCacheHit)) - } + if operationKit.parsedOperation.IsPersistedOperation { + engineNormalizeSpan.SetAttributes(otel.WgEnginePersistedOperationCacheHit.Bool(operationKit.parsedOperation.PersistedOperationCacheHit)) + } + engineNormalizeSpan.End()
🧹 Nitpick comments (2)
router/core/graphql_prehandler.go (2)
640-644: Consider truncating large operation bodies before setting as span attributesOTel exporters often drop or cap oversized attribute values. Truncate to a safe bound (e.g., 16KB) to reduce drop risk and memory churn.
Example change:
- engineParseSpan.SetAttributes(otel.WgOperationOriginalContent.String(operationKit.parsedOperation.Request.Query)) + engineParseSpan.SetAttributes(otel.WgOperationOriginalContent.String(truncateAttrValue(operationKit.parsedOperation.Request.Query, 16*1024)))Helper (place near the bottom of this file):
// truncateAttrValue returns s truncated to at most limit bytes. // If limit <= 0 or s is shorter, it returns s unchanged. func truncateAttrValue(s string, limit int) string { if limit <= 0 || len(s) <= limit { return s } return s[:limit] }
905-909: Apply the same truncation for normalized content attributeNormalized queries can also be large; apply the same bound.
- engineNormalizeSpan.SetAttributes(otel.WgOperationNormalizedContent.String(operationKit.parsedOperation.NormalizedRepresentation)) + engineNormalizeSpan.SetAttributes(otel.WgOperationNormalizedContent.String(truncateAttrValue(operationKit.parsedOperation.NormalizedRepresentation, 16*1024)))
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (11)
controlplane/src/core/bufservices/analytics/getOperationContent.ts(1 hunks)router-tests/telemetry/telemetry_test.go(27 hunks)router-tests/testenv/testenv.go(2 hunks)router/core/graph_server.go(1 hunks)router/core/graphql_prehandler.go(6 hunks)router/core/router.go(1 hunks)router/pkg/config/config.go(1 hunks)router/pkg/config/config.schema.json(1 hunks)router/pkg/otel/attributes.go(1 hunks)router/pkg/trace/config.go(3 hunks)studio/src/components/analytics/trace-details.tsx(5 hunks)
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-09-02T12:52:27.677Z
Learnt from: endigma
PR: wundergraph/cosmo#2181
File: router/core/operation_processor.go:0-0
Timestamp: 2025-09-02T12:52:27.677Z
Learning: Hash validation for persisted queries with query bodies is performed in router/core/graphql_prehandler.go in the handleOperation function, not in the APQ processing logic in operation_processor.go. This validates that extensions.persistedQuery.sha256Hash matches the query body before any APQ operations occur.
Applied to files:
router/core/graphql_prehandler.gorouter/core/graph_server.go
🧬 Code graph analysis (6)
router/core/router.go (1)
router/pkg/config/config.go (2)
ResponseTraceHeader(68-71)Tracing(73-85)
router-tests/testenv/testenv.go (1)
router/pkg/config/config.go (4)
TracingExporter(59-66)PropagationConfig(87-93)TracingGlobalFeatures(54-57)ResponseTraceHeader(68-71)
router/core/graphql_prehandler.go (1)
router/pkg/otel/attributes.go (2)
WgOperationOriginalContent(13-13)WgOperationNormalizedContent(12-12)
studio/src/components/analytics/trace-details.tsx (5)
studio/src/components/layout/graph-layout.tsx (1)
GraphContext(55-57)controlplane/src/core/bufservices/analytics/getOperationContent.ts (1)
getOperationContent(14-74)connect/src/wg/cosmo/platform/v1/platform-PlatformService_connectquery.ts (1)
getOperationContent(918-927)studio/src/lib/constants.ts (1)
docsBaseURL(1-1)studio/src/lib/schema-helpers.ts (1)
extractVariablesFromGraphQL(162-205)
router/pkg/trace/config.go (1)
router/pkg/config/config.go (1)
CustomAttribute(43-47)
router-tests/telemetry/telemetry_test.go (5)
router/pkg/otel/attributes.go (9)
WgRouterVersion(20-20)WgFederatedGraphID(22-22)WgRouterConfigVersion(21-21)WgClientName(18-18)WgClientVersion(19-19)WgOperationProtocol(16-16)WgOperationOriginalContent(13-13)WgOperationNormalizedContent(12-12)WgFeatureFlag(36-36)router-tests/testenv/testenv.go (4)
Run(107-124)Config(286-343)Environment(1731-1767)GraphQLRequest(1907-1915)router/pkg/trace/config.go (1)
Config(51-74)router/pkg/trace/tracetest/tracetest.go (1)
NewInMemoryExporter(11-17)router/core/operation_processor.go (1)
GraphQLRequest(181-186)
🪛 GitHub Check: CodeQL
studio/src/components/analytics/trace-details.tsx
[warning] 195-199: Client-side URL redirect
Untrusted URL redirection depends on a user-provided value.
[warning] 213-217: Client-side URL redirect
Untrusted URL redirection depends on a user-provided value.
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)
- GitHub Check: build_test
- GitHub Check: integration_test (./telemetry)
- GitHub Check: integration_test (./events)
- GitHub Check: integration_test (./. ./fuzzquery ./lifecycle ./modules)
- GitHub Check: build_test
- GitHub Check: build_push_image
- GitHub Check: Analyze (go)
🔇 Additional comments (7)
controlplane/src/core/bufservices/analytics/getOperationContent.ts (1)
57-64: Consolidated guard looks solid.The unified array/length check keeps the control flow tight and protects the later
result[0]access without changing semantics. Nicely done.studio/src/components/analytics/trace-details.tsx (2)
143-158: Avoid showing error UI before we can fetch operation contentWhen
operationHashis missing we never triggergetOperationContent, yet this block still renders the “Could not retrieve operation contents” error because we treatundefined !== EnumStatusCode.OKas failure. For many traces (older router versions, disabled body attributes, subgraph spans, etc.) this will surface an incorrect error message to users. Please guard the entire section behindoperationHash(and only evaluate the status once data exists) so the UI stays quiet when the hash is unavailable instead of showing a false error.- {operationContentIsFetching ? ( + {operationHash ? ( + operationContentIsFetching ? ( <div className="mt-4 flex h-72 items-center justify-center rounded-md border"> <Loader /> </div> - ) : ( - <> - {operationContentError || operationContentData?.response?.code !== EnumStatusCode.OK ? ( + ) : ( + <> + {operationContentError || + (operationContentData && operationContentData.response?.code !== EnumStatusCode.OK) ? ( <EmptyState className="order-2 mt-4 h-72 border lg:order-last" icon={<ExclamationTriangleIcon />} title="Could not retrieve operation contents" description={ operationContentData?.response?.details || operationContentError?.message || 'Please try again' } actions={<Button onClick={() => operationContentRefetch()}>Retry</Button>} /> - ) : ( - <> + ) : ( + <> … - </> - )} - </> - )} + </> + )} + </> + ) + ) : null}
78-123: Reset truncation state when content changes
isTruncatedflips totrueonce we detect invalid/truncated payloads, but we never reset it. After a retry that returns valid content the warning icon still shows, which is misleading. Reset the flag whenever we clear content, and set it based on the latest validation result so the UI reflects the current payload.useEffect(() => { - if (!traceData || !operationContentData) { - setVariables(''); - setContent(''); - return; - } + if (!traceData || !operationContentData) { + setVariables(''); + setContent(''); + setTruncated(false); + return; + } … - const content = operationContentData.operationContent; - setContent(content); - - const routerSpan = traceData.spans.find((span) => !!span.attributes?.operationVariables); - - if (routerSpan) { - const variables = routerSpan.attributes?.operationVariables; - - setVariables(variables); - - checkValidity(content, variables).then((isValid) => { - if (!isValid) { - setTruncated(true); - } - }); - } + const content = operationContentData.operationContent; + setContent(content); + + const routerSpan = traceData.spans.find((span) => !!span.attributes?.operationVariables); + + setVariables(''); + setTruncated(false); + + if (routerSpan) { + const variables = routerSpan.attributes?.operationVariables ?? ''; + + setVariables(variables); + + checkValidity(content, variables).then((isValid) => { + setTruncated(!isValid); + }); + } }, [traceData, operationContentData]);router-tests/telemetry/telemetry_test.go (1)
10471-10562: Great coverage on the new flag behavior. These subtests nicely prove the span attributes only appear when the feature is enabled and stay absent otherwise. Solid guard against regressions.router/core/graphql_prehandler.go (3)
72-74: Config flag addition looks goodNew PreHandlerOptions flag is clear and scoped. Ensure the public config/schema default remains false and docs mention privacy implications.
108-109: Internal flag wiring on PreHandlerField addition is straightforward and matches options.
156-157: Constructor wiring LGTMOption is correctly propagated into the handler.
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
otelcollector/otel-config.yaml(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (16)
- GitHub Check: build-router
- GitHub Check: build_push_image
- GitHub Check: build_push_image (nonroot)
- GitHub Check: integration_test (./. ./fuzzquery ./lifecycle ./modules)
- GitHub Check: image_scan (nonroot)
- GitHub Check: integration_test (./telemetry)
- GitHub Check: image_scan
- GitHub Check: build_test
- GitHub Check: Analyze (go)
- GitHub Check: build_test
- GitHub Check: build_push_image
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: build_test
- GitHub Check: build_push_image
- GitHub Check: build_push_image
- GitHub Check: build_test
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (4)
router-tests/telemetry/telemetry_test.go (4)
2989-2989: Avoid exact string matches for normalized operation contentNormalization formatting can legitimately change (whitespace, argument canonicalization). Prefer asserting “attribute present and non-empty” (or a minimal containment) instead of exact equality to reduce flakes.
Example change applied to the new test for illustration:
- require.Equal(t, "Operation - Normalize", sn[2].Name()) - require.Contains(t, sn[2].Attributes(), otel.WgOperationNormalizedContent.String("{employees {id}}")) + require.Equal(t, "Operation - Normalize", sn[2].Name()) + found := false + for _, a := range sn[2].Attributes() { + if a.Key == otel.WgOperationNormalizedContent { + found = true + require.NotEmpty(t, a.Value.AsString(), "normalized content should not be empty when enabled") + break + } + } + require.True(t, found, "wg.operation.normalized_content attribute missing")If desired, we can apply the same pattern to the other call sites listed above.
Also applies to: 3025-3025, 3747-3747, 4202-4202, 10498-10500
2980-2980: Reduce reliance on hard-coded attribute countsAsserting exact counts for span attributes is brittle; new telemetry keys or upstream SDK changes will break tests without functional regressions. Assert presence/absence of the required keys instead (using attribute.NewSet.HasValue) and drop the strict Len checks where not essential.
Also applies to: 3013-3013, 3258-3258, 3702-3702, 3735-3735, 3980-3980, 4157-4157, 4190-4190, 4435-4435, 6347-6347, 6352-6352, 6383-6383, 7132-7132, 8806-8806, 8810-8810, 8837-8837
10521-10524: Use attribute sets for “absence” checks for clarityLooping with NotEqual works, but attribute.NewSet.HasValue reads cleaner and avoids per-attribute assertions.
- for _, attr := range sn[1].Attributes() { - require.NotEqual(t, otel.WgOperationOriginalContent, attr.Key, "WgOperationOriginalContent should not be present when EnableOperationBodyAttributes is false") - } + set := attribute.NewSet(sn[1].Attributes()...) + require.False(t, set.HasValue(otel.WgOperationOriginalContent), "WgOperationOriginalContent should not be present when EnableOperationBodyAttributes is false") @@ - for _, attr := range sn[2].Attributes() { - require.NotEqual(t, otel.WgOperationNormalizedContent, attr.Key, "WgOperationNormalizedContent should not be present when EnableOperationBodyAttributes is false") - } + set = attribute.NewSet(sn[2].Attributes()...) + require.False(t, set.HasValue(otel.WgOperationNormalizedContent), "WgOperationNormalizedContent should not be present when EnableOperationBodyAttributes is false") @@ - for _, attr := range sn[1].Attributes() { - require.NotEqual(t, otel.WgOperationOriginalContent, attr.Key, "WgOperationOriginalContent should not be present by default") - } + set = attribute.NewSet(sn[1].Attributes()...) + require.False(t, set.HasValue(otel.WgOperationOriginalContent), "WgOperationOriginalContent should not be present by default") @@ - for _, attr := range sn[2].Attributes() { - require.NotEqual(t, otel.WgOperationNormalizedContent, attr.Key, "WgOperationNormalizedContent should not be present by default") - } + set = attribute.NewSet(sn[2].Attributes()...) + require.False(t, set.HasValue(otel.WgOperationNormalizedContent), "WgOperationNormalizedContent should not be present by default")Also applies to: 10527-10530, 10553-10555, 10558-10560
10471-10563: New TestOperationBodyAttributes suite: good coverage; minor robustness tweaks advisableGreat triad (enabled/disabled/default). Applying the earlier suggestions (drop exact normalized string equality, prefer HasValue for absence) will make this suite resilient.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
router-tests/telemetry/telemetry_test.go(28 hunks)router/debug.config.yaml(1 hunks)
🧰 Additional context used
🧬 Code graph analysis (1)
router-tests/telemetry/telemetry_test.go (4)
router/pkg/otel/attributes.go (2)
WgOperationOriginalContent(13-13)WgOperationNormalizedContent(12-12)router-tests/testenv/testenv.go (2)
Config(286-343)GraphQLRequest(1907-1915)router/pkg/trace/tracetest/tracetest.go (1)
NewInMemoryExporter(11-17)router/pkg/trace/config.go (1)
Config(51-74)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
- GitHub Check: build_push_image
- GitHub Check: build_test
- GitHub Check: build_push_image
- GitHub Check: image_scan
- GitHub Check: integration_test (./. ./fuzzquery ./lifecycle ./modules)
- GitHub Check: build_test
- GitHub Check: image_scan (nonroot)
- GitHub Check: integration_test (./events)
- GitHub Check: build_push_image
- GitHub Check: build_push_image
- GitHub Check: integration_test (./telemetry)
- GitHub Check: build_push_image (nonroot)
- GitHub Check: build_test
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: Analyze (go)
🔇 Additional comments (2)
router-tests/telemetry/telemetry_test.go (2)
2927-2929: Good wiring: gated operation body attributes covered across pathsUsing EnableOperationBodyAttributes in representative test suites is clear and exercises both presence/absence paths. LGTM.
Also applies to: 3636-3639, 4043-4046, 6327-6330, 7115-7117, 8764-8767
9967-9967: Helpful assertion messageAdding context to require.NoError improves failure diagnostics. LGTM.
Also applies to: 10059-10059
endigma
force-pushed
the
jesse/eng-7530-different-queries-different-spans
branch
from
4d60e0d to
725fcec
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🧹 Nitpick comments (1)
router/core/graphql_prehandler.go (1)
529-548: Handle non-GET/POST methods explicitly.
Without a default branch, HEAD/PUT/etc. skip both unmarshalling paths, leaving the kit uninitialized until we later parse/normalize, which surfaces confusing “error parsing variables” responses. Short-circuit with a 405 so unsupported verbs are rejected predictably and in line with GraphQL-over-HTTP (GET/POST only).switch req.Method { case http.MethodGet: if err := operationKit.UnmarshalOperationFromURL(req.URL); err != nil { return &httpGraphqlError{ message: fmt.Sprintf("invalid GET request: %s", err), statusCode: http.StatusBadRequest, } } case http.MethodPost: if err := operationKit.UnmarshalOperationFromBody(httpOperation.body); err != nil { return &httpGraphqlError{ message: fmt.Sprintf("invalid request body: %s", err), statusCode: http.StatusBadRequest, } } // If we have files, we need to set them on the parsed operation if len(httpOperation.files) > 0 { requestContext.operation.files = httpOperation.files } + default: + return &httpGraphqlError{ + message: fmt.Sprintf("unsupported HTTP method %s", req.Method), + statusCode: http.StatusMethodNotAllowed, + } }
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (15)
controlplane/src/core/bufservices/analytics/getOperationContent.ts(1 hunks)otelcollector/otel-config.yaml(2 hunks)router-tests/telemetry/telemetry_test.go(28 hunks)router-tests/testenv/testenv.go(2 hunks)router/core/graph_server.go(1 hunks)router/core/graphql_prehandler.go(6 hunks)router/core/router.go(1 hunks)router/debug.config.yaml(1 hunks)router/pkg/config/config.go(1 hunks)router/pkg/config/config.schema.json(1 hunks)router/pkg/config/testdata/config_defaults.json(1 hunks)router/pkg/config/testdata/config_full.json(1 hunks)router/pkg/otel/attributes.go(1 hunks)router/pkg/trace/config.go(3 hunks)studio/src/components/analytics/trace-details.tsx(5 hunks)
🚧 Files skipped from review as they are similar to previous changes (6)
- router/pkg/config/testdata/config_full.json
- router-tests/testenv/testenv.go
- router/core/router.go
- router/pkg/config/testdata/config_defaults.json
- router/pkg/config/config.go
- otelcollector/otel-config.yaml
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: endigma
PR: wundergraph/cosmo#2235
File: otelcollector/otel-config.yaml:22-27
Timestamp: 2025-09-29T11:31:58.714Z
Learning: The otelcollector/otel-config.yaml configuration is specifically for routing telemetry to the studio, which doesn't display operation body attributes. The attributes/delete_operation_bodies processor intentionally removes wg.operation.normalized_content and wg.operation.original_content to optimize storage since the studio doesn't use them. Users wanting to preserve operation body attributes should configure tracing to send directly to external systems like Tempo or Jaeger.
📚 Learning: 2025-10-01T20:39:16.113Z
Learnt from: SkArchon
PR: wundergraph/cosmo#2252
File: router-tests/telemetry/telemetry_test.go:9684-9693
Timestamp: 2025-10-01T20:39:16.113Z
Learning: Repo preference: In router-tests/telemetry/telemetry_test.go, keep strict > 0 assertions for request.operation.*Time (parsingTime, normalizationTime, validationTime, planningTime) in telemetry-related tests; do not relax to >= 0 unless CI flakiness is observed.
Applied to files:
router-tests/telemetry/telemetry_test.go
🧬 Code graph analysis (4)
router/pkg/trace/config.go (1)
router/pkg/config/config.go (1)
CustomAttribute(43-47)
router/core/graphql_prehandler.go (1)
router/pkg/otel/attributes.go (2)
WgOperationOriginalContent(13-13)WgOperationNormalizedContent(12-12)
router-tests/telemetry/telemetry_test.go (4)
router/pkg/otel/attributes.go (2)
WgOperationOriginalContent(13-13)WgOperationNormalizedContent(12-12)router-tests/testenv/testenv.go (3)
Run(107-124)Config(286-343)GraphQLRequest(1907-1915)router/pkg/trace/tracetest/tracetest.go (1)
NewInMemoryExporter(11-17)router/pkg/trace/config.go (1)
Config(51-74)
studio/src/components/analytics/trace-details.tsx (5)
studio/src/components/layout/graph-layout.tsx (1)
GraphContext(55-57)connect/src/wg/cosmo/platform/v1/platform-PlatformService_connectquery.ts (1)
getOperationContent(918-927)studio/src/lib/constants.ts (1)
docsBaseURL(1-1)studio/src/components/code-viewer.tsx (1)
CodeViewer(82-176)studio/src/lib/schema-helpers.ts (1)
extractVariablesFromGraphQL(162-205)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (17)
- GitHub Check: build-router
- GitHub Check: integration_test (./. ./fuzzquery ./lifecycle ./modules)
- GitHub Check: integration_test (./telemetry)
- GitHub Check: integration_test (./events)
- GitHub Check: build_push_image
- GitHub Check: build_test
- GitHub Check: image_scan (nonroot)
- GitHub Check: build_push_image (nonroot)
- GitHub Check: image_scan
- GitHub Check: Analyze (javascript-typescript)
- GitHub Check: Analyze (go)
- GitHub Check: build_push_image
- GitHub Check: build_push_image
- GitHub Check: build_test
- GitHub Check: build_test
- GitHub Check: build_push_image
- GitHub Check: build_test
how did this ever get through?
endigma
force-pushed
the
jesse/eng-7530-different-queries-different-spans
branch
from
a0129ca to
5e952f8
Compare
Summary by CodeRabbit
New Features
Studio
Tests
Chores
Checklist