Custom metrics

[charlienegri]

Summary: define custom metrics to be collected together with the standard ones from the prometheus-flask-exporter

Related issue: #220

Suggested reviewer(s):

Reviewer checklist:

• The headers of all files contain a reference to the repository license
• 100% test coverage of new code - meaning:
  • The overall test coverage increased or remained the same as before
  • Every function is accompanied with a test suite
  • Tests are both positive (testing that the function work as intended with valid data) and negative (testing that the function behaves as expected with invalid data, e.g., that correct exceptions are thrown)
  • Functions with optional arguments have separate tests for all options
• Examples are supported by doctests
• All tests are passing
• All names (e.g., files, classes, functions, variables) are explicit
• Documentation (as docstrings) is complete and understandable

The checklist is based on the S-ENDA conventions and definition of done (see General Conventions). The above points are not necessarily relevant to all contributions. In that case, please add a short explanation to help the reviewer.

[charlienegri]

@magnarem tested this running the container locally and it seems to work there at least...

[magnarem]

Approved. Merging