Determine modelling of slot reduction hypothesis

[amc-ie]

Luis has created an export of all of the current prometheus metrics available as it stands. https://o1-labs.slack.com/archives/C079ESVGB9T/p1719415934021519 The next step is to try and map these to our desired modelling criteria and then prioritize any gaps there might be.

The desired metrics are captured here: https://docs.google.com/document/d/1OsXH_RlCfXG04ZbVV9SwmorOyFPPeFpMCV4144lI75I/edit#heading=h.s89qd1ufj0uj

[submarinec94]

from Luis - I think a considerable % of those would be to understand what these are for, currently to retrieve all metrics

scope concern --- currently thousands of metrics (including cryptography metrics ...)

currently metrics don't have descriptions? metrics generated via automated mechanism

first step

• work w/ code, figure out type of metrics (w/ abstract summary)
• document metrics
• short description of metrics

Second step:

• descriptions in code and included in dashboard for usage

relevant resource:

1. https://grafana.gcp.o1test.net/d/fwefsdfsf23rfef/simplified-testnet-overview?orgId=1&refresh=1m&from=1721236770894&to=1721323170894
2. https://grafana.gcp.o1test.net/d/4BrFOXyMk/alerts?orgId=1&refresh=5s&from=1721301587884&to=1721323187884

[Geometer1729]

Another resource: https://github.com/MinaProtocol/mina/blob/develop/src/lib/mina_metrics/prometheus_metrics/mina_metrics.ml

[submarinec94]

break down task for modeling from alan:

Investigate daemon metrics to determine how we can reach desired model state (@Brian Kuhns) Create a Grafana dashboard based on the modelling metrics (Brian with @Luis Sanabria)

https://o1-labs.slack.com/archives/C079ESVGB9T/p1721251596359619

[Geometer1729]

It turns out by running a local node with --metrics-port 3086 You can curl the metrics enpoint for all the help info curl localhost:3086/metrics | grep '#HELP' | sed -e "s/^\#HELP //;s/ /,/" > out.csv I uploaded the csv as a new page in the spreadsheet and used it to lookup descriptions for many of the metrics.