tally
tally copied to clipboard
uber-go
A Go metrics interface with fast buffered metrics and third party reporters
…hat it is easier to test. Add the number of values and durations in order to enable easier histogram testing
Go [launched](https://go.dev/blog/go1.20) Profile-Guided Optimization (PGO) with v1.20. With this, inlining optimization now uses a threshold called `inlineHotMaxBudget` which has a default value of 2000 for PGO-based inlining [Line 76, [inl.go](https://github.com/golang/go/blob/master/src/cmd/compile/internal/inline/inl.go)]....
Hey folks, I'm trying to get some clarification on Histogram reporting for prometheus metrics. A sample histogram metric in Prometheus format looks like ``` # HELP http_request_duration_seconds Api requests response...
It seems that bad names will cause panics, see: https://github.com/uber-go/tally/issues/198 This is less than ideal since metrics names can be generated at runtime, and more graceful failure handling is preferable...
The `scope.Counter`, `scope.Gauge`, `scope.Timer` funcs sanitize the name before cache lookups, which can add significant overhead. It would be nice to do sanitize after cache lookups instead - this is...
Despite this comment: https://github.com/uber-go/tally/blob/a80396bb6850d098eea5088ac37f5d208cf3b034/stats.go#L374-L377 I just saw this panic: ``` panic: runtime error: index out of range [101] with length 101 goroutine 1904106 [running]: github.com/uber-go/tally.(*histogram).RecordValue(0xc000161810, 0x3bd1507?) external/com_github_uber_go_tally/stats.go:381 ``` The panic...
## error I noticed we cannot upgrade past 4.1.10 because we get this error in our tests > panic: descriptor Desc{fqName: "tally.internal.counter_cardinality", help: "tally.internal.counter_cardinality gauge", constLabels: {}, variableLabels: [version host...
