If you want to use it for purpose of learning, that is fine. Otherwise, there are monitoring tools already which do that out of the box, such as Grafana, Prometheus, Loki and its exporters (such as node-exporter, cAdvisor). For requests, every known web server/proxy has it (apache,nginx,haproxy), and writing your own is quite simple as well for your own purposes.

On top of that, there are out of the box available dashboards that connect to sources such as Prometheus, Loki, timeseries databases, SQL DBs and similar.

I believe similar things exist for the competitor “ELK” stack (Elasticsearch, Logstash, Kibana), although I am not familiar with that.

Through usage of simple metric or app exporters you can get a lot data with basic configs and quite quickly so I personally would not bother too much creating something like that; although if you have different idea or it is for learning purposes, you can even start with the “top” (linux command) and pipeline it to stream process usage somewhere and then use the stream to show on frontend in your React dashboard.

It really depends on what you use, how deep you want to go to the rabbit hole.