The cleanup of the old counters is done so it can be closed

The computation of those metrics will be executed in production on a regular basis, probably each day, to keep them up to date.

Improve the readability of the graphs

In T3127#67581, @anlambert wrote:

    I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?

Indeed there is something weird here as we have more than one million gitlab.com origins in database.

softwareheritage=> select count(*) from origin where url like 'https://gitlab.com/%';
  count  
---------
 1023499
(1 row)

Looks like something was missed when computing lister metrics from scheduler database, this needs further investigations.

Indeed, please do look into this, thanks.

Thanks for these details: this count is missing the 800k git origins: @ardumont and @olasd should be able to tell you how to find them

In T3127#67581, @anlambert wrote:

I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?

Indeed there is something weird here as we have more than one million gitlab.com origins in database.

softwareheritage=> select count(*) from origin where url like 'https://gitlab.com/%';
  count  
---------
 1023499
(1 row)

Looks like something was missed when computing lister metrics from scheduler database, this needs further investigations.

I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?

I am a bit puzzled by the numbers shown: eeally we have only 200k origins for GitLab.com.?
And we know we had some 1.5m origins for Google code, why only 700k shown here?

Instead, we could split the coverage widget into two tabs

• one giving a high level overview of the archived origins, similar to what we have now with logos and counters
• one giving the details of all forges we archived so far, displayed in a table as you suggested with relevant metrics and links to search origins for a given forge

I think we could also get an accurate count of deposit origins (HAL, IPOL) using swh-deposit API

Only one nit about the display. Using modal windows/popover will mean that there will be no easy way to have, as a user, the full list: one will have to click on each logo one by one, which could be quite annoying. Would it be possible to have a page with a rendering of the table above? (not sure if we want all columns, but at least the last update time and the number of origins per forge instance looks relevant and interesting to me). It coule be either in addition of what you propose (e.g., as a "coverage details" link, leading to the full page), or as a replacement of it (e.g., by making each forge icon just a link to the relevant anchor within the table on the "coverage details" page).

Thanks for this update, great work!

Some reports of what have been done so far and some future directions regarding the display of those data in swh-web.

A fundraising campaign can now be easily created and configured from the WP admin dashboard, closing this.

the decision is to create a GitLab repository dedicated to writing the FAQ (Ambassadors can do PR or add issues dedicated to the FAQ)

• the repository will contain a faq-website.md file that can be easily exported into html with the correct tags per question
• concerning the devs/users/sys-admins FAQ, they will be directly edited in the docs
• if issues on the FAQ repository will concern devs/users/sys-admins
  • these issues will be tagged and resolved with addition on the docs instance

T3397#66758 allow the deployment to be done.

In T3127#66684, @anlambert wrote:

As @olasd said in a previous comment, even if we compute the metrics, we will miss counters about origins not tight to a lister
(googlecode and gitorious for instance). So I am thinking again about an hybrid approach using the swh-counters metrics
implemented yersteday which gives a rough estimation on the number of origins by network location (as visit statuses are not
processed, only origins) and the scheduler metrics.

In T3127#66673, @ardumont wrote:

I guess the cli to update metrics is executed periodically in production ?

I don't think that they are yet but that just got a priority increase now ;)

I guess the cli to update metrics is executed periodically in production ?

The existing scheduler metrics are probably not complete enough for all we want to display (we should review them so they are), but the swh.scheduler journal client already gathers all the information needed, so we > should be able to compute all that we need from the scheduler tables.

After more thoughts about all those metrics, we could revamp the coverage widget into two tabs:

• one tab displaying metrics about loaded origins with detailed counts by forge and links to search interface to browse them
• one tab displaying metrics about listed origins from the data extracted from the scheduler database

In T3127#66665, @ardumont wrote:

@anlambert @rdicosmo

For information, discussing with @olasd, he reminded me that we had already a cli entrypoint [1]
to compute stats about what we want scheduler side.

What's missing implementation wise would be to expose an endpoint to actually display said information.

So, the question is, even though the implementation swh.counter started, do we really want that there
or this ^ scheduler side would be enough?

[1] https://forge.softwareheritage.org/source/swh-scheduler/browse/master/swh/scheduler/cli/origin.py$148-182

Sorry @anlambert, I was late at Monday's meeting and I completely missed this in your weekly plan, I would have pointed this out earlier.

For information, discussing with @olasd, he reminded me that we had already a cli entrypoint [1]
to compute stats about what we want scheduler side.