Create Metric Registry

[IvanIvanoff]

Changes

Create a Metric Registry that is replacing the static JSON files used to define Clickhouse metrics.

The old way

Before, to expose a clickhouse metric through the API, a JSON map describing the metric needed to be added to a JSON file here in the repository, looking like this:

{
  "human_readable_name": "USD Trading Volume",
  "name": "volume_usd_5m",
  "metric": "trading_volume",
  "version": "2019-01-01",
  "access": "free",
  "selectors": [
    "slug"
  ],
  "min_plan": {
    "SANAPI": "free",
    "SANBASE": "free"
  },
  "aggregation": "last",
  "min_interval": "5m",
  "table": "intraday_metrics",
  "has_incomplete_data": false,
  "data_type": "timeseries",
  "docs_links": ["https://academy.santiment.net/metrics/trading-volume"]
}

The new way

Now the metrics definitions are moved to Postgres and a web interface is exposed to edit/create metrics.
The WEB interface is accessed through VPN and after credentials are obtained.
The endpoints are:

• Stage: http://sanbase-admin.stage.san:31080/admin2/metric_registry
• Prod: http://sanbase-admin.production.san:31080/admin2/metric_registry

Showing metric details

Show all the details for a metric. The same fields as in the JSON file are exposed. Some of the fields are slightly renamed (aggregation -> default aggregation) or split (min_plan is not a map, but there are 2 fields: Sanbase Min Plan and Sanapi Min Plan)

Editing metrics

The metric information can be edited through the Web interface.
A big benefit of the web interface compared to the JSON files is that the changes are validated in real-time.

Ticket

Checklist:

• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have tried to find clearer solution before commenting hard-to-understand parts of code
• I have added tests that prove my fix is effective or that my feature works