Skip to content

Releases: grafana/node_exporter

0.18.1 Grafana Release 2

10 Feb 09:52
20dddf4
Compare
Choose a tag to compare

Node Exporter release with --web.extra-headers flag.

To add arbitrary headers to the HTTP response for / and /metrics, run node_exporter --web.extra-headers=Foo=bar:

$ curl -vq http://localhost:9100/metrics
* TCP_NODELAY set
* Connected to localhost (::1) port 9100 (#0)
> GET /metrics HTTP/1.1
> Host: localhost:9100
> User-Agent: curl/7.64.1
> Accept: */*
> 
< HTTP/1.1 200 OK
< Content-Type: text/plain; version=0.0.4; charset=utf-8
< Foo: bar
< Date: Mon, 10 Feb 2020 09:53:54 GMT
< Transfer-Encoding: chunked
< 
{
# HELP go_gc_duration_seconds A summary of the GC invocation durations.
# TYPE go_gc_duration_seconds summary
go_gc_duration_seconds{quantile="0"} 0
...

The flag can be repeated to add multiple headers.

0.18.1 Grafana Release 1

30 Jan 16:52
Compare
Choose a tag to compare

Node Exporter release with HTTPS support.

When running a server with TLS use the flag --web.config

e.g. ./node_exporter --web.config="web-config.yml"

The config file should be written in YAML format, and is reloaded on each connection to check for new certificates and/or authentication policy.

Sample Config:

tlsConfig :
  # Certificate and key files for server to use to authenticate to client
  tlsCertPath : <filename>
  tlsKeyPath : <filename>

  # Server policy for client authentication. Maps to ClientAuth Policies
  # For more detail on clientAuth options: [ClientAuthType](https://golang.org/pkg/crypto/tls/#ClientAuthType)
  [ clientAuth : <string> | default = "NoClientCert" ]

  # CA certificate for client certificate authentication to the server
  [ clientCAs : <filename> ]