sitespeedio / sitespeedio/sitespeed.io
Accessibility Violations sending Issues and not Violation counts to InfluxDB
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5k
- Forks
- 624
- Avg merge
- 4h 8m
- Merged PRs (30d)
- 2
Description
Your question
Hi
I am trying to set up Accessibility violations in Grafana and based off the violations to send alerts but the counts of the Issues are sent to the InfluxDB and not actual counts of the Violations. The default thresholds are set based off the Violations and not Issues, unless I am wrong here.
Is there a way to fix this where Violations counts are sent to the InfluxDB or both, issues and violations.
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 by comparing the accessibility metrics shown in Grafana with the issue and violation counts written to InfluxDB, using the screenshots and the default thresholds described in the report. Trace where these accessibility values are produced and stored; the issue is done when the documented or implemented metric behavior matches the intended violation thresholds, with both counts available if supported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grafana
- Domain
- accessibility, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100