Graphite data not visible after running Sitespeed.io with Graphite configuration

Hi team,

I’m running my Sitespeed.io script using the following Docker command:
docker run --rm --shm-size=2g -v "%cd%":/sitespeed.io sysco/qperf-sitespeed:37.5.1
sitespeed.io /sitespeed.io/duck.js --headless --browsertime.chrome.args no-sandbox
--outputFolder /sitespeed.io --multi -n 1
--graphite.host host.docker.internal
--graphite.port 2003
--graphite.namespace sitespeed_io.default
--graphite.addSlugToKey true
--slug duckTest

The run completes successfully, and I can see the HTML report generated locally.
However, I don’t see any data being pushed or reflected in my Graphite database.

What I expected:
The metrics should appear under the configured namespace in Graphite (sitespeed_io.default) after the test run.

What actually happened:
No new data points are visible in Graphite.

I verified that the Graphite service is reachable on port 2003 and working for other data sources.

Could you please help me identify if this is a configuration issue or a known bug with Graphite publishing?

Start by reproducing the Docker command with sitespeed.io/duck.js and the supplied Graphite options, then inspect the run output and Graphite endpoint for publishing errors. Done means the run publishes new data points under the sitespeed_io.default namespace and the behavior is covered by an appropriate regression check.