The only munin metric that an external tool depends on is the object
counter[6], which is exported from munin to the main website to make the
graphs. The object counter needs to be moved to prometheus, and the export
pipeline needs to be rewritten to use a prometheus query. This should be fairly
trivial as we already use the prometheus sql exporter for other metrics[7,8].[6] http://munin.internal.softwareheritage.org/softwareheritage.org/prado.softwareheritage.org/softwareheritage_objects_softwareheritage.html
[7] https://github.com/credativ/sql_exporter
[8] https://forge.softwareheritage.org/source/puppet-swh-site/browse/production/data/hostname/prado.softwareheritage.org.yaml$8-33
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Migrated | gitlab-migration | T1356 Kill munin | ||
| Migrated | gitlab-migration | T1355 Move the object counter from munin to prometheus | ||
| Migrated | gitlab-migration | T1434 Refactor prometheus SQL exporter configuration generation to use latest version from elephant shed | ||
| Migrated | gitlab-migration | T1437 Rewrite the munin stats export for the website to use prometheus | ||
| Migrated | gitlab-migration | T1436 Integrate swh-storage metrics in prometheus |
Event Timeline
Comment Actions
Even though it is not necessarily obvious, the object counter has been stored in Prometheus since December 2018.
- The web page http://belvedere.internal.softwareheritage.org:9100/metrics doesn't contain any instance of "sql_swh_archive_object_count"
- A request on http://pergamon.internal.softwareheritage.org:9090/graph does howewer return some data. sql_swh_archive_object_count{object_type="content"} is a good test request.