[Journeys] Set traceparent for Playwright #189800

dgieselaar · 2024-08-02T13:51:32Z

Sets the traceparent for Playwright, so the trace from the test runner includes the trace events from the browser and Kibana server.

obltmachine · 2024-08-02T13:51:49Z

🤖 GitHub comments

Expand to view the GitHub comments

Just comment with:

/oblt-deploy : Deploy a Kibana instance using the Observability test environments.
run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)

dgieselaar · 2024-08-03T13:05:18Z

This needs elastic/apm-agent-rum-js#1521 to really work - currently the browser transaction becomes the root transaction and the parent of the backend transaction/span, and in the Journey setup, that means that you can no longer navigate the full trace from the perspective of the test runner.

…ce-context

dgieselaar · 2024-08-27T07:58:13Z

I have verified elastic/apm-agent-rum-js#1521 works, and the initial page load is associated with the first step from the journey. However, when the page load transaction expires, and new managed transactions are started (e.g. based on an http request or a user interaction event), a new trace ID will be generated, and we can no longer see these events in the trace waterfall. I have reached out to the agent devs to see if there is a solution for that.

…ce-context

dgieselaar · 2024-08-27T10:08:36Z

Pushed a change that uses page.evaluate() to override trace.id and parent.id on every created Transaction. It's a private API so not sure if it's sustainable, will discuss with the agent folks.

afharo · 2024-08-27T18:33:14Z

packages/core/rendering/core-rendering-server-internal/src/get_apm_config.ts

@@ -45,7 +45,8 @@ export const getApmConfig = (requestPath: string) => {
      ...config,
      pageLoadTraceId: traceId,
      pageLoadSampled: sampled,
-      pageLoadSpanId: backendTransaction.ensureParentId(),


Q: should we keep this one and use the other ones only as fallbacks?

pageLoadSpanId inverses the relationship - the RUM page-load transaction becomes the parent of the transaction on the backend. I still don't get what the use case is for this (or maybe I forgot), to me it makes more sense to have the server transaction to render the HTML be the parent of the page-load transaction. What are your thoughts here?

TBH, I'm not familiar with why we did this and what ensureParentId() does. I'm mostly concerned about breaking the current behavior (I'm not sure if it's already broken 😅).

What you're saying makes a lot of sense to me. However, as I was trying to understand what this parameter does, I found this piece of documentation recommending the use of ensureParentId as the pageLoadSpanId on dynamically generated HTML.

Unless anyone is depending on the fact that the RUM transaction is the parent of the backend transaction (I honestly can't think of a use case for this), I think we can safely change this. However, I've reverted this change so we don't have to wait until elastic/apm-agent-rum-js#1521 is merged.

Both serve different purpose, For all APM agents (before Synthetics existed) RUM transaction is always considered the root.

So whenever the HTML is rendered from the Server, the Original Navigation timing span Requesting and Receiving the document will include the timing spent on the backend server which captures the time between requestStart and responseEnd. This is the part where the pageLoadSpanId helps where we can tie the frontend navigation with the backend HTML response generation.

Post Synthetics world, we need a new way to keep the RUM transaction as a child of the Synthetics one since browser is started from the synthetics side (Lots of details are in this issue - [Proposal] Crosslinking Synthetics with APM synthetics#265). This PR feat: add pageLoadParentId configuration apm-agent-rum-js#1521 solves this linking by creating a new option to override the RUM parent trace.

Hope this helps.

…ce-context

kibana-ci · 2024-08-30T07:30:56Z

💛 Build succeeded, but was flaky

Buildkite Build
Commit: 739c9ea

Failed CI Steps

Metrics [docs]

✅ unchanged

History

💛 Build #230366 was flaky 52dc0c5
💔 Build #230047 failed 011cc4b
💛 Build #229694 was flaky e1311ea
💛 Build #225590 was flaky 35630ea

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

…ce-context

dmlemeshko · 2024-09-03T08:47:32Z

posting update for visibility:

After running journeys on CI, we still have an error and missing kibana server traces. Example for dashboard_listing_page journey

We are waiting for the RUM agent PR with required changes to be merged.

vigneshshanmugam · 2024-09-11T19:08:31Z

packages/kbn-journeys/journey/journey_apm_config.ts

@@ -15,7 +15,7 @@ export const JOURNEY_APM_CONFIG = {
  secretToken: APM_PUBLIC_TOKEN,
  active: 'true',
  contextPropagationOnly: 'false',
-  environment: process.env.CI ? 'ci' : 'development',
+  environment: process.env.ELASTIC_APM_ENVIRONMENT || (process.env.CI ? 'ci' : 'development'),


Not sure if its required, ENV variables overrides everything by default on the agent level? If this is for RUM agent, then yes its needed.

yes, it's for the RUM agent

vigneshshanmugam · 2024-09-11T19:18:07Z

packages/kbn-journeys/journey/journey_ftr_harness.ts

+            return;
+          }
+          win.traceIdOverrideListenerAttached = true;
+          win.elasticApm!.observe('transaction:start', (tx) => {


there is a high chance this gets changed before transaction:end gets fired. Better would be to do it at that time.

…ce-context

elasticmachine · 2025-01-03T13:06:23Z

💚 Build Succeeded

Buildkite Build
Commit: bcacb7a

Metrics [docs]

✅ unchanged

[Journeys] Set traceparent for Playwright

35630ea

dgieselaar added release_note:skip Skip the PR/issue when compiling release notes v8.16.0 labels Aug 2, 2024

dgieselaar requested review from a team as code owners August 2, 2024 13:51

jbudz approved these changes Aug 2, 2024

View reviewed changes

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

e1311ea

…ce-context

dgieselaar added 2 commits August 27, 2024 12:07

Override trace id/parent id with page.evaluate()

dc54f76

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

011cc4b

…ce-context

dgieselaar requested a review from a team as a code owner August 27, 2024 10:07

afharo reviewed Aug 27, 2024

View reviewed changes

dgieselaar added 4 commits August 28, 2024 11:20

Fix tests

8a34ca6

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

52dc0c5

…ce-context

Use pageLoadSpanId for now

559dbbd

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

739c9ea

…ce-context

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

77a1983

…ce-context

vigneshshanmugam reviewed Sep 11, 2024

View reviewed changes

dgieselaar added 2 commits January 3, 2025 09:15

Merge branch 'main' of github.com:elastic/kibana into journey-ftr-tra…

95891e4

…ce-context

Use pageLoadParentId again

a943791

dgieselaar added v9.0.0 backport:version Backport to applied version labels v8.18.0 and removed v8.16.0 labels Jan 3, 2025

Merge branch 'main' into journey-ftr-trace-context

bcacb7a

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Journeys] Set traceparent for Playwright #189800

[Journeys] Set traceparent for Playwright #189800

dgieselaar commented Aug 2, 2024

obltmachine commented Aug 2, 2024

dgieselaar commented Aug 3, 2024

dgieselaar commented Aug 27, 2024

dgieselaar commented Aug 27, 2024

afharo Aug 27, 2024

dgieselaar Aug 28, 2024

afharo Aug 28, 2024

dgieselaar Aug 30, 2024

vigneshshanmugam Sep 11, 2024

kibana-ci commented Aug 30, 2024

dmlemeshko commented Sep 3, 2024

vigneshshanmugam Sep 11, 2024

dgieselaar Dec 30, 2024

vigneshshanmugam Sep 11, 2024

elasticmachine commented Jan 3, 2025

[Journeys] Set traceparent for Playwright #189800

Are you sure you want to change the base?

[Journeys] Set traceparent for Playwright #189800

Conversation

dgieselaar commented Aug 2, 2024

obltmachine commented Aug 2, 2024

🤖 GitHub comments

dgieselaar commented Aug 3, 2024

dgieselaar commented Aug 27, 2024

dgieselaar commented Aug 27, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

kibana-ci commented Aug 30, 2024

💛 Build succeeded, but was flaky

Failed CI Steps

Metrics [docs]

History

dmlemeshko commented Sep 3, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

elasticmachine commented Jan 3, 2025

💚 Build Succeeded

Metrics [docs]