EVEREST-507 Report metrics

[oksana-grishchenko]

Collect and report metrics

Problem:
EVEREST-507

Report the db engines metrics - how many db clusters of each type are running.

A step forward multi k8s support - generate own Everest ID instead of using the k8s cluster ID.

The telemetry request example

CHECKLIST

Jira

• Is the Jira ticket created and referenced properly?

Tests

• Is an Integration test/test case added for the new feature/change?
• Are unit tests added where appropriate?

[recharte]

Overall the code looks good but I'm not entirely sure that having a table called settings with a single ID column is the best long term solution.
Maybe we should go with a key value approach that will not only cover our current use-case of storing the unique everest instance ID but will allow us to expand it to any other settings that we need to store like default values for a DB engine configuration or whatever.
What do you think about this?

[oksana-grishchenko]

Maybe we should go with a key value approach that will not only cover our current use-case of storing the unique everest instance ID but will allow us to expand it to any other settings that we need to store like default values for a DB engine configuration or whatever.

@recharte thanks for the suggestion, the key-value approach sounds great. Updated, PTAL

[recharte]

Looks great 💪