Page MenuHomeSoftware Heritage

Metrics/monitoringTag
ActivePublic

Members

  • This project does not have any members.
  • View All

Watchers

  • This project does not have any watchers.
  • View All

Recent Activity

Fri, Dec 3

ardumont placed T1481: add metric to monitor "save code now" efficiency up for grabs.
Fri, Dec 3, 3:57 PM · Save Code Now, System administration, Metrics/monitoring
ardumont moved T1481: add metric to monitor "save code now" efficiency from deployed/landed to Backlog on the System administration board.
Fri, Dec 3, 3:57 PM · Save Code Now, System administration, Metrics/monitoring

Aug 26 2021

olasd merged T1278: swh-journal: the monitoring tool question! into T2128: Monitor journal consumer lag.
Aug 26 2021, 12:30 PM · Metrics/monitoring, Sprint 2019/12 (Monitor and Conquer)
olasd added a comment to T2128: Monitor journal consumer lag.

This would have caught T3502 earlier too.

Aug 26 2021, 12:27 PM · Metrics/monitoring, Sprint 2019/12 (Monitor and Conquer)

Aug 3 2021

ardumont added a comment to T3127: Compute and display distribution of origins by forge.

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

Aug 3 2021, 5:00 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
ardumont added a revision to T3127: Compute and display distribution of origins by forge: D6052: Install update-metrics as a service called daily.
Aug 3 2021, 2:32 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 29 2021

ardumont changed the status of T3402: Deploy swh-counters v0.8.0 and backfill origins, a subtask of T3127: Compute and display distribution of origins by forge, from Wontfix to Resolved.
Jul 29 2021, 1:24 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
ardumont changed the status of T3402: Deploy swh-counters v0.8.0 and backfill origins from Wontfix to Resolved.
Jul 29 2021, 1:24 PM · Counters, System administration, Metrics/monitoring

Jul 23 2021

anlambert added a comment to T3127: Compute and display distribution of origins by forge.
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.

Jul 23 2021, 12:17 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 22 2021

anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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

Jul 22 2021, 12:29 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
rdicosmo added a comment to T3127: Compute and display distribution of origins by forge.

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.

Jul 22 2021, 9:01 AM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 21 2021

anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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

Jul 21 2021, 5:26 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
rdicosmo added a comment to T3127: Compute and display distribution of origins by forge.

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?

Jul 21 2021, 3:40 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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
Jul 21 2021, 3:23 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 19 2021

anlambert added a revision to T3127: Compute and display distribution of origins by forge: D6007: common/utils: Wrap deposits list retrieval in a function.
Jul 19 2021, 5:29 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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

Jul 19 2021, 3:54 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 16 2021

anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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).

Jul 16 2021, 11:43 AM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
zack added a comment to T3127: Compute and display distribution of origins by forge.

Thanks for this update, great work!

Jul 16 2021, 11:29 AM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 13 2021

anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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

Jul 13 2021, 3:39 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Jul 9 2021

olasd changed the status of T3403: Use forge URL network location as default lister instance name, a subtask of T3127: Compute and display distribution of origins by forge, from Open to Work in Progress.
Jul 9 2021, 3:37 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert closed T3402: Deploy swh-counters v0.8.0 and backfill origins, a subtask of T3127: Compute and display distribution of origins by forge, as Wontfix.
Jul 9 2021, 2:34 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert closed T3402: Deploy swh-counters v0.8.0 and backfill origins as Wontfix.

Precise metrics about listed origins and their counts will be retrieved from the scheduler database, no need to backfill origins with swh-counters then, closing this.

Jul 9 2021, 2:34 PM · Counters, System administration, Metrics/monitoring

Jun 23 2021

olasd added a comment to T3127: Compute and display distribution of origins by forge.

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.

Jun 23 2021, 9:16 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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 ;)

Jun 23 2021, 2:08 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
ardumont added a comment to T3127: Compute and display distribution of origins by forge.

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

Jun 23 2021, 1:59 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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.

Jun 23 2021, 12:49 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

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
Jun 23 2021, 12:13 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.
Jun 23 2021, 12:05 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

@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

Jun 23 2021, 12:04 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
olasd added a comment to T3127: Compute and display distribution of origins by forge.

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.

Jun 23 2021, 12:04 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
ardumont added a comment to T3127: Compute and display distribution of origins by forge.

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.

Jun 23 2021, 11:53 AM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert triaged T3402: Deploy swh-counters v0.8.0 and backfill origins as Normal priority.
Jun 23 2021, 11:13 AM · Counters, System administration, Metrics/monitoring

Jun 22 2021

anlambert added a revision to T3127: Compute and display distribution of origins by forge: D5910: journal_client: Add origins processing.
Jun 22 2021, 4:50 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a revision to T3127: Compute and display distribution of origins by forge: D5907: interface: Add get_listers method.
Jun 22 2021, 2:36 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

Nice to see this moving forward!

These entries in the counter log look suspicious, though, they are not origins:

b'atlassian@bitbucket.org' 2
b'taylorhakes@github.com' 2
b'bunnyhero@bitbucket.org' 1
b'dtrebbien@bitbucket.org' 1
b'eldargab@github.com' 1
b'git@github.com' 1
b'schierlm@git.code.sf.net' 1
b'tomakehurst@github.com' 1
b'wenshao@github.com' 1
b'zimbra-mirror@bitbucket.org' 1
Jun 22 2021, 2:05 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
rdicosmo added a comment to T3127: Compute and display distribution of origins by forge.

Nice to see this moving forward!

Jun 22 2021, 1:59 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

Regarding this, to ease the mapping between a lister and an instance name, we may want to rework the instance names in the scheduler
model (listers table) so that the value is actually the netloc of the origin.

Jun 22 2021, 12:18 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
ardumont added a comment to T3127: Compute and display distribution of origins by forge.

Great work! Awesome.

Jun 22 2021, 12:16 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task
anlambert added a comment to T3127: Compute and display distribution of origins by forge.

After some analysis, the data we need to properly implement this are:

  • the set of lister names and their instance names in order to organize origins by forge types (gitlab, cgit, sourceforge, ...)
  • a precise or estimated count for the origins listed by a given lister instance
Jun 22 2021, 12:07 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

May 28 2021

ardumont added a comment to T1481: add metric to monitor "save code now" efficiency.

Now what's missing here (not sure how hard it is) is the mean and max ingestion time
of save code now requests (time between they being accepted and the loader task is
over)

May 28 2021, 11:54 AM · Save Code Now, System administration, Metrics/monitoring

Apr 23 2021

vlorentz assigned T1363: Have metrics in prometheus for each tracked forge to olasd.
Apr 23 2021, 4:52 PM · Roadmap 2021, Metrics/monitoring, System administration
vlorentz assigned T3127: Compute and display distribution of origins by forge to anlambert.
Apr 23 2021, 4:52 PM · Metrics/monitoring, Web app, Roadmap 2021, meta-task

Apr 20 2021

ardumont added a project to T1481: add metric to monitor "save code now" efficiency: Save Code Now.
Apr 20 2021, 4:42 PM · Save Code Now, System administration, Metrics/monitoring
ardumont added a comment to T1481: add metric to monitor "save code now" efficiency.

Note that there is the same transient vs cumulative discrepency on the "Accepted requests" graph.

Apr 20 2021, 4:35 PM · Save Code Now, System administration, Metrics/monitoring
ardumont added a comment to T1481: add metric to monitor "save code now" efficiency.

I think the "submitted requests per visit type / status" graph should be split in 2 parts. Both accepted and rejected are cumulative values that will indefinitely grow, while pending are transient value aiming at staying near zero, so it makes no sense to have them on the same graph.

Since there is already a graph dedicated to pending requests, then pending reas should just be removed from the submitted reas graph.

Apr 20 2021, 4:26 PM · Save Code Now, System administration, Metrics/monitoring
douardda added a comment to T1481: add metric to monitor "save code now" efficiency.

Note that there is the same transient vs cumulative discrepency on the "Accepted requests" graph.

Apr 20 2021, 11:06 AM · Save Code Now, System administration, Metrics/monitoring
douardda added a comment to T1481: add metric to monitor "save code now" efficiency.

I think the "submitted requests per visit type / status" graph should be split in 2 parts. Both accepted and rejected are cumulative values that will indefinitely grow, while pending are transient value aiming at staying near zero, so it makes no sense to have them on the same graph.

Apr 20 2021, 11:02 AM · Save Code Now, System administration, Metrics/monitoring
douardda added a comment to T1481: add metric to monitor "save code now" efficiency.

I think the "submitted requests per visit type / status" graph should be split in 2 parts. Both accepted and rejected are cumulative values that will indefinitely grow, while pending are transient value aiming at staying near zero, so it makes no sense to have them on the same graph.

Apr 20 2021, 11:00 AM · Save Code Now, System administration, Metrics/monitoring

Apr 12 2021

ardumont moved T1481: add metric to monitor "save code now" efficiency from Backlog to deployed/landed on the System administration board.
Apr 12 2021, 3:56 PM · Save Code Now, System administration, Metrics/monitoring
ardumont added a project to T1481: add metric to monitor "save code now" efficiency: System administration.
Apr 12 2021, 3:56 PM · Save Code Now, System administration, Metrics/monitoring