Print some stats before saving probe data to disk

Open Beginner friendly
#13 12 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
data-engineering

Research direction

Read runner.py and locate the path that saves probe outputs to disk. Trace the extracted probe data and version or revision information, then add a summary immediately before saving. Done means the output reports counts for each probe type and the number of versions or revisions processed.

Written by the indexing model from the issue text.

Description

enhancement good-first-bug help wanted priority:4

To make it more easy to judge whether things worked correctly etc., it would be great to print some basic stats before saving the outputs to disk in runner.py.
E.g.:

  • how many probes of each type we have (histograms, scalars, events, ...)
  • how many versions/revisions we extracted data for
Dominant language
Python
Stars
26
Forks
73
Avg merge
10h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/probe-scraper

All issues in mozilla/probe-scraper

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.