Plugin uses wrong field when writing metrics to InfluxDB
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 42/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- observability-sre
Research direction
Start by tracing the plugin's InfluxDB metric-writing path and compare its verbose-log output with the sitespeed core example. Use the Lighthouse and Grafana examples as references; done means the emitted metrics use the intended measurement or series field rather than relying on the audit tag.
Written by the indexing model from the issue text.
Description
Hi there. I noticed that the plugin writes its metrics to InfluxDB differently than the core sitespeed app. This way you have to query the data in very unorthodox ways. See difference in sitespeed verbose log:
Sitespeed core:
(correctly uses series name for the measurement)
{
"tags": {
"device": "desktop",
"stage": "produktion",
"origin": "browsertime",
"summaryType": "summary",
"connectivity": "native",
"browser": "chrome",
"group": "www_enbw_com",
"testName": "www_enbw_com"
},
"seriesName": "firstPaint",
"point": {
"time": 1630409179532,
"median": 483
}
},
Lighthouse plugin:
(uses extra "audit" tag for the actual series name...and the series name is the unit???)
{
"tags": {
"audit": "first-contentful-paint",
"device": "desktop",
"stage": "produktion",
"origin": "lighthouse",
"summaryType": "pageSummary",
"page": "_unternehmen_",
"group": "www_enbw_com",
"testName": "www_enbw_com"
},
"seriesName": "numericValue",
"point": {
"time": 1630409179532,
"value": 1454.0010000000002
}
},
Also see the difference in Grafana query:
Any chance, this will be fixed in the future?
Cheers!
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
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.
More from sitespeedio/plugin-lighthouse
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
sitespeedio/plugin-lighthouse#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#134 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#133 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#126 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#120 · 7 comments ·
All issues in sitespeedio/plugin-lighthouse
Similar issues
-
bug confirmed issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
open-webui/open-webui#30750 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 70/100