prometheus-plugs
prometheus-plugs copied to clipboard
deadtrickster
Prometheus.erl Elixir Plugs
Hi! Thanks for the lib! I'm getting this when compiling: ```shell warning: Plug.Builder.compile/3 defined in application :plug is used by the current application but the current application does not depend...
Hey, I tried switching from `:microseconds` to `:seconds` since Prometheus suggests to use `second` as base unit. The problem is, the config setting only changes the metric name but not...
`use Prometheus.PlugPipelineInstrumenter` The code above triggers the following warning: `warning: System.stacktrace/0 is deprecated, use __STACKTRACE__ instead` on Elixir 1.11[.2]. This is a problem because we use `mix compile --warnings-as-errors` in...
In my `rel/config/config.exs` I set ```elixir config :prometheus, ValiotApp.PrometheusExporter, auth: {:basic, System.get_env("METRICS_USER"), System.get_env("METRICS_PASS")} ``` But PrometheusExporter isn't using this configuration. If I instead set it on `config/prod.exs` it uses the...
The current exporter plug is serving metrics on given path (`/metrics` by default), or passing the conn. This is for plug pipeline... and it doesn't work for phoenix router! ```elixir...
Declaring a counter does not mean it exists, as it will only have a value after the first inc. So, the fist time a counter is bumped it goes from...
This change should reasonably prevent timing attacks against http auth in "/metrics" endpoint. The current implementation does nothing to prevent timing attacks against the equality check in `valid_basic_credentials?`.
In case several services use pushegateway name collisions may occur. So I suggest making them configurable.
Now than Phoenix 1.4 has been released and it's defaulting to use Telemetry (https://github.com/beam-telemetry/telemetry) may be a good idea to integrate it so every metric managed by telemetry shows up...
