- Fix duplicate counter errors on VLC reloads (#70 @LorenzoPeri)
- Match cache hit rate calculation in example dashboard to match Varnish internals (#73] @dhpowrhost)
- Start building releases with go 1.17.4
- Varnish 6.5.x support (#64 @johanneswuerbach)
- Update github.com/prometheus/client_golang dependency to v1.9.0
- Remove GOARCH=386 builds from releases
- Start building releases with go 1.15.6
- Fix metric names and missing labels for file cache metrics (#55 @thedustin)
- Fix scraping for Varnish 3.x. Removes the
main_n_ban
grouping. Metrics will now have individualbans_<type>
metrics instad of the grouped metric that hadtype
as a label. (#51 @glennslaven)- If you previously updated to 1.5 your exports would have already been broken as the grouping tries to combine gauge and counter metrics, which is not allowed by Prometheus.
- This is breaking change if you are using Varnish 3.x and use ban metrics in your dashboards, you'll need to update them to the new ones.
- Clean exported backend name if beginning with reload_ (#56 @stromnet)
- Fix incorrectly typing Varnish 4.0.x stat flag
a
metrics as gauges instead of counters. (#48 @glennslaven) - Fix
-test
mode to wait for full metrics scrape before continuing.
- Deprecate
-no-exit
. Default behavior is now not to exit on scrape errors as it should be for a long running HTTP server.- This was design misstep. You will now get a deprecation warning if you pass
-no-exit
but the process behaves as before. - New explicit
-exit-on-errors
has been added for users who want the old default behavior back.
- This was design misstep. You will now get a deprecation warning if you pass
- Correctly export gauge and counter types from
varnishstat
outputtype
property. - Add go module support.
- Use
github.com/prometheus/client_golang
v1.0.0 - Start building releases with go 1.12.6
-docker-container-name
to signal thatvarnishstat
should be ran in a docker container withdocker exec <container-name>
.- Support Varnish 6.0.0 by testing the main logic works and metrics are exported.
- Start building releases with go 1.10.3
- Standard non Varnish prometheus metrics need to now be enabled with
-with-go-metrics
. Before they were included by default. Now dropped to export less clutter that majority of users will never need (@nipuntalukdar). - Fix
varnish_backend_up
with Varnish 4.0 and earlier versions.
- New per backend metric
varnish_backend_up
with 1/0 value that reflects the latest health probe result. The Varnish bitmap uint64varnish_backend_happy
as a prometheus float metric was not that useful in detecting latest up/down per backend. - Ability to give custom path to varnishstat with
-varnishstat-path
(@zstyblik) - Github releases now include Grafana dashboards archive. This includes all the dashboards posted by users in the repo, starting with my own.
- New
-no-exit
mode that does not exit the process if varnish is not running at the time of startup. - Support Varnish 5.2 that removed
type
andident
properties from varnishstat JSON output. Ifident
is not present, it is now parsed from the metric name. - Add tests to run scrape on static json files.
- Start building releases with go 1.9.1
- Update readme to mention that exporter has been tested to work against Varnish 5.x releases.
- Start building releases with go 1.9
- Don't return a 400 for
/
to behave more like other Prometheus exporters out there. Can now be used for health checks. (#15) - Start building releases with go 1.8
- Release packages now use the same naming and internal structure scheme with promu.
- Fixes issues running this exporter with systems like puppet-prometheus
- No code changes
- Start building releases with go 1.7.5
- Fix VBE label inconsistencies by always having
backend
andserver
labels present. (#5 #8) - Resulted in varnish reporting lots of errors for a while after VCL reloads.
- Fix bugs in
backend
andserver
label value parsing from VBE ident. (#5 #8) - Add travis-ci build and test integration. Also auto pushes cross compiled binaries to github releases on tags.
-web.health-path <path>
can be configured to return a 200 OK response, by default not enabled. #6- Start building releases with go 1.7.3
- First official release
- Start building releases with go 1.7.1