Would it be nice to document `Registry`, `Collector` and metric classes?

Hi guys. Thanks for providing this great library for making monitoring fun and easy in python. It's my Day 1 with this package. The README provided a very quick introduction but I was also puzzled at the following question:

1. Seems we defined some metric classes, but not assigned to any other things. The web server was started but it seemed magical that the server somehow knows the metric class objects.

This puzzle was gone after I checked out the source codes (which is very fun to read, thanks!) and realized that there's a global REGISTRY object. The server app takes a registry object which is by default the global REGISTRY, and each Collector object, in the __init__ method, also accepts a registry object, which by default is also REGISTRY.

I think it would be nice if there could be some API reference sections/pages. I'd be glad to contribute such a section, but would like to hear any comment from the community, like the necessity, proposed format, etc.

Cheers!

Commencez par examiner le README et les zones du code source contenant la REGISTRY globale, Registry, Collector, les classes de métriques et l’application serveur. Clarifiez la portée et le format préférés par la communauté pour la référence d’API avant de rédiger. Le travail est terminé lorsque la référence convenue explique comment les registres et les collecteurs relient les classes de métriques à l’application serveur.