🔷 Define key benchmarks and monitoring metrics for Core team

[walnut-the-cat]

Goals

Background

The project aims to provide clear understanding on current states of components the team owns and incremental value each project adds.

Why should NEAR One work on this

Currently, there are two missing major missing parts in our product/feature development cycle:

• We do not have a set of defined benchmarks to run before releasing a feature. Everyone follows their own judgement and conclude whether they have done enough testing/benchmarking to confirm improvement and no regression.
• We do not have a set of defined key metrics to monitor and understand health of components we own. For example, no one can clearly state whether our current storage or network is 'performant and stable enough'

As the team matures, it is critical for us to have more structured pipeline to 1) make our released feature more stable 2) measure and monitor improvements the team is making over time.

What needs to be accomplished

The goals of this project are as follows:

• The team has clear steps to follow before feature release to understand expected outcome of each feature after mainnet release
• The team has clear understanding of health of the components the team owns

To achieve the goals, these are the key items that need to be accomplished:

• Identify key benchmarks we need to run before feature release for each domain: Chain, Storage, Network
• Align on the feature development and release process with the team and document
• Identify key metrics to understand health of the areas the team owns
• Set up Grafana dashboard for the team with those metrics

[walnut-the-cat]

Other than aligning on two team level metrics, no major progress. The project is currently blocked due to other higher priorities.