mirror of
https://github.com/hikhvar/mqtt2prometheus.git
synced 2026-02-14 18:09:53 +00:00
126e13428b
As mentioned in https://github.com/hikhvar/mqtt2prometheus/issues/23, we do not use any logging framework at all. This was fine for getting the exporter startet. However, with inreasing load the logging must be configureable. This PR is a start to replace all instances of "log.Printf" with the zap logger. The current configuration parameters are the log level and the log format (console, json). We might expose the log configuration to the config file. But I think this is overkill for the current state of the exporter.
21 lines
656 B
Modula-2
21 lines
656 B
Modula-2
module github.com/hikhvar/mqtt2prometheus
|
|
|
|
go 1.14
|
|
|
|
require (
|
|
github.com/beorn7/perks v1.0.1
|
|
github.com/eclipse/paho.mqtt.golang v1.1.1
|
|
github.com/golang/protobuf v1.4.0
|
|
github.com/matttproud/golang_protobuf_extensions v1.0.1
|
|
github.com/patrickmn/go-cache v2.1.0+incompatible
|
|
github.com/prometheus/client_golang v1.6.0
|
|
github.com/prometheus/client_model v0.2.0
|
|
github.com/prometheus/common v0.9.1
|
|
github.com/prometheus/procfs v0.0.11
|
|
github.com/thedevsaddam/gojsonq v2.3.0+incompatible // indirect
|
|
github.com/thedevsaddam/gojsonq/v2 v2.5.2
|
|
go.uber.org/zap v1.16.0
|
|
golang.org/x/net v0.0.0-20190620200207-3b0461eec859
|
|
gopkg.in/yaml.v2 v2.2.5
|
|
)
|