Official Go implementation of the Ethereum protocol

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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
..
collector.go	metrics: add cpu counters (#26796)	2 years ago
collector_test.go	metrics: add cpu counters (#26796)	2 years ago
prometheus.go	metrics: add cpu counters (#26796)	2 years ago