Skip to content

docs: add browser profiling section to Blackfire guide #46

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.

Sign up for GitHub

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

Merged
navarr merged 2 commits into from
Mar 26, 2026
Merged

docs: add browser profiling section to Blackfire guide #46

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
b1d5fa0
docs: add browser profiling section to Blackfire guide
lbajsarowicz Mar 22, 2026
eca3af3
docs: wrap Chrome limitation in warning admonition box
lbajsarowicz Mar 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 20 additions & 1 deletion configuration/blackfire.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,4 +19,23 @@ Note: You can obtain the IDs and Tokens used in the above from within your Black

To use the Blackfire CLI Tool, you can run `warden blackfire [arguments]`.

For more information on the CLI tool, please see [Profiling CLI Commands](https://blackfire.io/docs/cookbooks/profiling-cli) in Blackfire's documentation.
For more information on the CLI tool, please see [Profiling CLI Commands](https://blackfire.io/docs/cookbooks/profiling-cli) in Blackfire's documentation.

## Browser Profiling

Blackfire provides browser extensions that let you profile any page directly from the toolbar. Install the extension for your browser, log in to your Blackfire account, navigate to the page you want to profile, and click the **Profile** button in the extension.

For a full walkthrough, see [Profiling HTTP Requests with a Browser](https://docs.blackfire.io/profiling-cookbooks/profiling-http-via-browser) in Blackfire's documentation.

### Browser extensions

* [Firefox extension](https://docs.blackfire.io/integrations/browsers/firefox) — **recommended**, supports all profiling features including **Profile all requests** (POST, Ajax, API calls)
* [Chrome extension](https://docs.blackfire.io/integrations/browsers/chrome) — single-page profiling works, but **Profile all requests** is unavailable (see below)

### Chrome limitation

:::{warning}
Chrome's Manifest V3 restricts extensions from modifying outgoing request headers, which breaks the **Profile all requests** feature. Chrome can only profile the initial page load — it cannot capture follow-up POST requests, Ajax calls, or API requests within a session. Single-page profiling still works normally.

If your workflow relies on profiling all requests in a session, **use Firefox** where this feature remains fully supported. For more details, see [Announcing changes to the "Profile all requests" feature on Chrome](https://blog.blackfire.io/announcing-changes-to-the-profile-all-requests-feature-on-chrome.html) on the Blackfire blog.
:::
Loading