1

我正在尝试main()为存储库运行该函数，但在变量初始化时遇到了棘手的恐慌：

> go run main.go
go: finding github.com/myorg/some-repo/emulator latest
go: finding github.com/myorg/some-repo latest
panic: duplicate metrics collector registration attempted

goroutine 1 [running]:
github.com/prometheus/client_golang/prometheus.(*Registry).MustRegister(0xc0002a09b0, 0xc00033a1d0, 0x1, 0x1)
    /Users/kurt/go/pkg/mod/github.com/prometheus/client_golang@v1.5.1/prometheus/registry.go:400 +0xad
github.com/prometheus/client_golang/prometheus/promauto.Factory.NewGaugeVec(0x1acee40, 0xc0002a09b0, 0x0, 0x0, 0x0, 0x0, 0x19ade0e, 0x21, 0x19c60fa, 0x56, ...)
    /Users/kurt/go/pkg/mod/github.com/prometheus/client_golang@v1.5.1/prometheus/promauto/auto.go:306 +0x118
github.com/prometheus/client_golang/prometheus/promauto.NewGaugeVec(0x0, 0x0, 0x0, 0x0, 0x19ade0e, 0x21, 0x19c60fa, 0x56, 0x0, 0xc000370160, ...)
    /Users/kurt/go/pkg/mod/github.com/prometheus/client_golang@v1.5.1/prometheus/promauto/auto.go:197 +0xa9
github.com/myorg/some-library/pubsub.init.ializers()
    /Users/kurt/go/pkg/mod/github.com/myorg/some-library@v0.0.0-20200404213659-0e93c264015a/pubsub/gcp.go:30 +0xcd
exit status 2

错误归结为这行代码：

var inFlightMetric     = promauto.NewGauge(prometheus.GaugeOpts{Name: "gcp_pubsub_handlers_running_count"})

我认为问题在于，同一个库也有一个pubsub/v2/gcp.go相同的行，因此程序试图导入两者github.com/myorg/some-library/pubsub并github.com/myorg/some-library/pubsub/v2在 Prometheus 指标收集器中遇到由“名称冲突”引起的恐慌。

我想做的是找到正在导入的依赖项github.com/myorg/some-library/pubsub并将其替换pubsub/v2为避免这种名称冲突。但是，我在弄清楚如何从这个堆栈跟踪中确定这一点时遇到了麻烦。关于如何实现这一目标的任何想法？

4

1 回答 1

0

我最终通过avoid-registering-duplicate-metrics-collector在库模块中创建一个分支并从该分支导入它来解决这个问题：

go get github.com/myorg/some-lib@avoid-registering-duplicate-metrics-collector

在那个分支中，我为包中_v1注册的所有指标附加了一个后缀，pubsub以避免名称冲突pusub/v2。不过，这有点小技巧，需要定期将主分支合并到该分支中以使其保持最新。找出导入中的哪个文件实际上正在尝试导入pubsub包的方法仍然有用。

于 2020-04-09T16:23:43.403 回答