Tool that makes Firefox Telemetry probe information searchable
Перейти к файлу
Jan-Erik Rediger 36f14f47a9 Check that history is set and has elements
It could be empty when `showReleaseOnly` is selected, leading to an
error that blanks the whole page.

Fixes #142
2024-05-15 15:00:59 +02:00
cypress address most review concerns 2019-07-25 14:22:57 -05:00
public update the favicon properly 2020-05-28 22:54:24 -05:00
src Check that history is set and has elements 2024-05-15 15:00:59 +02:00
.dockerignore Fix build + tweaks 2020-12-08 17:12:56 -08:00
.env update env file to reflect new path for 2 data sources 2019-10-17 12:44:18 -05:00
.gitignore Fix build + tweaks 2020-12-08 17:12:56 -08:00
CODE_OF_CONDUCT.md address most review concerns 2019-07-25 14:22:57 -05:00
Dockerfile Fix build + tweaks 2020-12-08 17:12:56 -08:00
LICENSE Initial commit 2016-11-30 01:02:55 +01:00
README.md address most review concerns 2019-07-25 14:22:57 -05:00
babel.config.js Add jest tests for snakeCase 2020-12-08 15:16:28 -08:00
cypress.json implement initial cypress integration testing 2019-06-21 17:04:09 -05:00
package.json Enable OpenSSL legacy providers in scripts 2023-02-06 12:39:26 +01:00
yarn.lock Bump axios from 0.19.2 to 0.21.1 2023-02-06 12:37:32 +01:00

README.md

probe-dictionary

A tool that makes the Telemetry probe data in Firefox more discoverable and searchable.

This front-end allows answering questions like

  • "do we have any probes in Firefox 55 that tell us about tab usage?"
  • "which Firefox versions is this probe in anyway?"

To achieve this, it uses data extracted by the probe-scraper project. This pulls probe registry files (Histograms.json, Scalars.yaml, Events.yaml) from different Firefox versions together into one dataset. Also, probes outside of Histograms.json - like the CSS use counters - are included in the output data.

Currently this supports:

  • release, beta & nightly channels
  • major releases only
  • all probes registered in separate files (histograms, scalars, events)
  • some select environment data points (more to come)

This project was bootstrapped with Create React App.

Development

To run locally:

run npm start To launch the cypress test runner: run npm run test

The production data endpoints should work just fine locally.