Request priority in HAR file for Chromium based browsers by ozcoder · Pull Request #164 · cloudflare/telescope

ozcoder · 2026-03-02T05:59:42Z

Adds _priority and _initialPriority to the HAR file when testing with a Chromium based browser.

Closes #16

Store the initial priority of each request. Store if the priority changes. Insert the initial priority value into the HAR file. Insert the final priority value into the HAR file.

Set types correctly on newPriorities and priorities. Check before using variables. Removed console debugging. Added fields to HarEntry.

sufian-cf · 2026-03-09T18:59:38Z

The change itself looks reasonable, but I'm not able to verify it locally. How can I run telescope so that there are _priority and _initialPriority fields produced within the har?

ozcoder · 2026-03-10T07:21:05Z

@sufian-cf if you run from the command line
npx . -u https://www.cloudflare.com/ -b chrome --timeout 60000 --debug
it will generate the files in a sub directory of the results directory.
Inside that is the pageload.har file which you can make pretty however you want (command or online) to make it easier to read. Eg. cat pageload.har | jq . > pageload.har.json
Edit that JSON file and search for a url entry that has Hero-globe as part of the filename. At the end of its entry it should have "_initialPriority": "Low" and the _priority value should be different, probably High since the browser would want to upgrade the priority of that image.
Other images would be upgraded too, but not all of them.

MildMax

verified working order of the initialPriority , priority, and resourceType in the chrome browser

sergeychernyshev

Looks like a good solution, we can make a couple improvements, see comments below.

Also, if you can make a fixture for testing the case with changing priority, it would be great. And maybe for testing duplicate requests.

Create mapping of hash of url and starting time to requestId. Gather resourceType is a better place. Fixup types.

sufian-cf · 2026-04-16T13:50:46Z

@@ -16,6 +17,34 @@ class ChromeRunner extends TestRunner {
  async createPage(browser: BrowserContext): Promise<Page> {
    const page = browser.pages()[0];
    const client: CDPSession = await page.context().newCDPSession(page);
+    await client.send('Network.enable');


Is it possible Network.requestWillBeSent / other events below will fire before this client.send('Network.enable')?

Shouldn't happen since even preparePage hasn't been called until the end of this method.

sufian-cf · 2026-04-16T14:38:31Z

Hey @ozcoder, my apologies for the delay. I've taken a look at this approach and have manually verified that it sometimes works, but not for all requests. I've left a few comments, and overall am a bit concerned with the approach.

That being said, I think this has surfaced a real bug in our existing code. If the page load triggers multiple requests with the same URL, we're going to only be updating performance information on the first one, since we look up the corresponding entry via findIndex on just the URL.

I've just created #243 and will follow up with a fix that introduces a unique id per request we can use to match things.

sufian-cf · 2026-04-16T21:32:32Z

Ok, I have a PR for the fix in #243 which should give each request a unique identifier that can be used to cross-reference: #244

Once that mechanism is used, and there's some automated test coverage verifying the presence of the priority fields in the HAR, this PR should be good to get in

…t universes. Can just use this instead of occasion. Do not need responseReceived event handler.

ozcoder · 2026-05-02T15:45:04Z

Hey @ozcoder, my apologies for the delay. I've taken a look at this approach and have manually verified that it sometimes works, but not for all requests. I've left a few comments, and overall am a bit concerned with the approach.

That being said, I think this has surfaced a real bug in our existing code. If the page load triggers multiple requests with the same URL, we're going to only be updating performance information on the first one, since we look up the corresponding entry via findIndex on just the URL.

I've just created #243 and will follow up with a fix that introduces a unique id per request we can use to match things.

Changed to use telescopeId .

Added testing of priorities recorded in the HAR file. Removed uneeded rawTmings.

ozcoder · 2026-05-06T10:31:13Z

@sufian-cf @sergeychernyshev I have changed the code to use telescopeId and added a test.
npm run test priority to run it. I'm not sure what else to add to this change.

MildMax · 2026-05-06T14:28:47Z

@ozcoder apologies, closed by accident

Added compression option to createStaticServer. Show launchTest error if not successful. Fixed wrong alt information for small images. Tweeked test page design with some breakpoints.

ozcoder · 2026-05-10T14:23:54Z

@MildMax With the test server, I have added the ability to delay the responses to simulate processing time. I also added a compression option, which adds some jitter to the processing time and might be useful for other tests. To see why the GitHub CI might not be happy, I now show launchTest error if not successful.

ozcoder added 6 commits December 6, 2025 17:30

Enable getting Network events from the Chrome Devtools Protocol Session.

8fca6f3

Store the initial priority of each request. Store if the priority changes. Insert the initial priority value into the HAR file. Insert the final priority value into the HAR file.

Merge branch 'main' into request_priority

a4b7834

Merge branch 'main' into request_priority

4635990

Tidyup

bbe0298

Merge branch 'main' into request_priority

ce9fb36

Renamed variables to be like other ones.

732b58a

Set types correctly on newPriorities and priorities. Check before using variables. Removed console debugging. Added fields to HarEntry.

ozcoder requested a review from a team March 2, 2026 05:59

sergeychernyshev added the ticket This label indicates that internal ticket was created to track it. label Mar 2, 2026

MildMax previously approved these changes Mar 16, 2026

View reviewed changes

sergeychernyshev requested changes Mar 19, 2026

View reviewed changes

Comment thread src/chromeRunner.ts Outdated

Comment thread src/chromeRunner.ts Outdated

Comment thread src/testRunner.ts

Comment thread src/chromeRunner.ts Outdated

ozcoder added 2 commits March 22, 2026 12:30

Merge branch 'main' into request_priority

10af114

Use requestId as key to priorities.

6577666

Create mapping of hash of url and starting time to requestId. Gather resourceType is a better place. Fixup types.

ozcoder dismissed MildMax’s stale review via 6577666 March 22, 2026 10:27

ozcoder requested a review from sergeychernyshev March 22, 2026 10:32

sufian-cf reviewed Apr 16, 2026

View reviewed changes

Comment thread packages/telescope/src/chromeRunner.ts Outdated

sufian-cf reviewed Apr 16, 2026

View reviewed changes

Comment thread packages/telescope/src/chromeRunner.ts Outdated

sufian-cf reviewed Apr 16, 2026

View reviewed changes

ozcoder added 2 commits May 1, 2026 19:16

Merge branch 'main' into request_priority

29ef5eb

Use the telescope-id header value as the ID between CDP and Playwrigh…

28ac9de

…t universes. Can just use this instead of occasion. Do not need responseReceived event handler.

Created a generic web server for testing.

c90d217

Added testing of priorities recorded in the HAR file. Removed uneeded rawTmings.

ozcoder requested a review from sufian-cf May 6, 2026 10:33

MildMax closed this May 6, 2026

MildMax reopened this May 6, 2026

Added ability to delay the response to simulate processing.

b3a217d

Added compression option to createStaticServer. Show launchTest error if not successful. Fixed wrong alt information for small images. Tweeked test page design with some breakpoints.

ozcoder requested a review from MildMax May 10, 2026 14:24

Conversation

ozcoder commented Mar 2, 2026

Uh oh!

sufian-cf commented Mar 9, 2026

Uh oh!

ozcoder commented Mar 10, 2026

Uh oh!

MildMax left a comment

Choose a reason for hiding this comment

Uh oh!

sergeychernyshev left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sufian-cf Apr 16, 2026

Choose a reason for hiding this comment

Uh oh!

ozcoder Apr 17, 2026

Choose a reason for hiding this comment

Uh oh!

sufian-cf commented Apr 16, 2026

Uh oh!

sufian-cf commented Apr 16, 2026

Uh oh!

ozcoder commented May 2, 2026

Uh oh!

ozcoder commented May 6, 2026

Uh oh!

MildMax commented May 6, 2026

Uh oh!

ozcoder commented May 10, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants