sitespeedio / sitespeedio/sitespeed.io
my repeated test dosen't show in grafan
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
hi dears, i'm very thanksful about sitespeed.io and enjoy it when i work with, i have written a multi scripting test with below configuration, but when i run test with one slug name it seems metrics overwritten and when i choose different slug name it's goes appear, how can i resolve this?
{
"browsertime": {
"iterations": 1,
"browser": "chrome",
"chrome": {
"traceCategories": "-*,disabled-by-default-lighthouse,v8,v8.execute,blink.user_timing,devtools.timeline,disabled-by-default-devtools.timeline,disabled-by-default-devtools.timeline.stack,disabled-by-default-devtools.timeline.frame,disabled-by-default-devtools.timeline.invalidationTracking,loading,latencyInfo"
}
},
"slug": "shouldBeUnique",
"graphite": {
"host": "172.31.54.69",
"port": 2003,
"httpPort": 18080,
"auth": "guest:guest",
"namespace": "sitespeed_io.desktop",
"logReceivedData": true
},
"metrics": {
"filter": [
"coach.pageSummary.advice.performance.adviceList.*.score",
"coach.pageSummary.advice.bestpractice.adviceList.*.score",
"coach.pageSummary.advice.accessibility.adviceList.*.score"
]
},
"axe": {
"enable": true
},
"utc": false
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied browsertime, slug, graphite, metrics, and axe configuration, then reproduce repeated runs in Grafana. Trace whether the same slug and namespace cause metrics to be overwritten; done means repeated tests remain separately visible under the intended slug behavior and the result is documented or fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100