3 Commits (80b7bfe70de59356a547c5a5e1c64f0a69e3873e)

Author	SHA1	Message	Date
turboboost55	7dc100714d	metrics: add cpu counters (#26796) ... This PR adds counter metrics for the CPU system and the Geth process. Currently the only metrics available for these items are gauges. Gauges are fine when the consumer scrapes metrics data at the same interval as Geth produces new values (every 3 seconds), but it is likely that most consumers will not scrape that often. Intervals of 10, 15, or maybe even 30 seconds are probably more common. So the problem is, how does the consumer estimate what the CPU was doing in between scrapes. With a counter, it's easy ... you just subtract two successive values and divide by the time to get a nice, accurate average. But with a gauge, you can't do that. A gauge reading is an instantaneous picture of what was happening at that moment, but it gives you no idea about what was going on between scrapes. Taking an average of values is meaningless.	2 years ago
Justin Traglia	2c5648d891	all: fix some typos (#25551) ... * Fix some typos * Fix some mistakes * Revert 4byte.json * Fix an incorrect fix * Change files to fails	2 years ago
Maxim Krasilnikov	31bc2a2434	metrics/prometheus: expose metrics in prometheus format too (#17077) ... * metrics/prometheus: added prometheus http server and metrics collector * metrics/prometheus: minor cleanups * metrics/prometheus: named keys instead name in tag * metrics/prometheus: minor typo cleanups, sorted report	6 years ago