Version 2.1.1 / 2020-04-12

Fix the GitHub Action to upload the correct binaries.

Version 2.1.0 / 2020-04-12

• Add a GitHub Action to upload the binaries for a new release.
• Build and push Docker image to ricoberger/script_exporter for a new release.

docker run -p 9469:9469 -v ~/script_exporter:/opt ricoberger/script_exporter:v2.1.0 -config.file /opt/config.yaml

Version 2.0.1 / 2019-12-13

• Fix prefix on HELP and TYPE tags
• Do not force {} for metrics

Version 2.0.0 / 2019-08-08

Breaking Changes

• Hard-coding the script endpoint as /probes (#9).
• Always run script: programs directly, removing the -config.shell command line option (#9).
• Rename the active parameters in the configuration to enabled (#13).

Features

• Expose internal metrics for script_exporter on /metrics (#9).
• Timeout (#12):
  • Use the timeout passed by Prometheus.
  • Reduce the timeout slightly to account for overhead.
  • The timeout from Prometheus can be overwritten via the configuration file.
  • The timeout is passed to the scripts via environment variable $SCRIPT_TIMEOUT.
  • The timeout can be enforced.
• Add configuration reload. The configuration will be reloaded if a SIGHUP signal is sent to the script_exporter process (#13).

Improvements

• Add build instructions for ARMv7 architecture to the Makefile (#10).
• Improve the authentication handling (#13).
• Add graceful shutdown. Shutdown is handled by SIGINT and SIGTERM signals (#13).

tls:
-  active: <boolean>
+  enabled: <boolean>
  crt: <string>
  key: <string>

basicAuth:
-  active: <boolean>
+  enabled: <boolean>
  username: <string>
  password: <string>

bearerAuth:
-  active: <boolean>
+  enabled: <boolean>
  signingKey: <string>

scripts:
  - name: <string>
    script: <string>
+    timeout:
+      max_timeout: <float>
+      enforced: <boolean>

Version 1.3.0 / 2019-07-04

• Feature: Direct run
  Add the ability to directly execute configured scripts. A big thanks goes to @siebenmann for this idea (#5) and his PR (#6)

• Improvements
  Improve the documentation and versioning.

Version 1.2.0 / 2018-12-12

Switch from dep to go modules for dependency management.

Version 1.1.2 / 2018-09-16

Add the possibility to use multiple arguments in the configuration file:

scripts:
  - name: helloworld
    script: ./examples/helloworld.sh test

The parameter test is passed to the script helloworld.sh now.

Version 1.1.1 / 2018-08-24

• Add output parameter
  The output parameter controls the handlign of the executed script output. If the parameter is set to ignore the output of the executed script is ignored and the script exporter only returns script_success{} and script_duration_seconds{}.

Version 1.1.0 / 2018-08-17

• New prefix handling
  In v1.0.0 the prefix was automatically set to script if the parameter was not provided. In v1.1.0 there would not be set a prefix if the parameter is not provided

• Add parameters option
  Pass params parameter to the script exporter, which contains parameters that should be passed to the script. An example is the ping script, where the target parameter is passed to the script.

• Add tls support
  If the tls support is activated in the configuration file, the script exporter is served via https. There for you must specify the path to the signed certificate (crt) and private key to the certificate (key) in the configuration.

• Add basic auth support
  If the basic auth support is activated, the script exporter is accessible only with basic authentication. The username and password is provided via the configuration file.

• Add bearer token authentication support
  If the bearer token authentication support is activated, the script exporter is accessible only with a bearer token. The signing key (signingKey) is provided via the configuration file.
  You can generate a bearer token for a signing key with the following command: ./bin/script_exporter -create-token

Version 1.0.0 / 2018-08-10

This is the first release of the script exporter. The script exporter is a Prometheus exporter to execute scripts and collect metrics from the output or the exit status. The scripts to be executed are defined via a configuration file. In the configuration file several scripts can be specified. The script which should be executed is indicated by a parameter in the scrap configuration. The output of the script is captured and is provided for Prometheus. Even if the script does not produce any output, the exit status and the duration of the execution are provided.