Go to file
Jan Christian Grünhage 0f3dc4ee21 chore: bump version to 0.4.0 and update changelog 2021-04-23 09:55:28 +02:00
src chore: replace homegrown errors with anyhow 2021-04-23 09:51:11 +02:00
.gitignore hopefully finish implementation 2019-02-06 19:30:33 +01:00
.gitlab-ci.yml Add .gitlab-ci.yml 2019-02-06 18:38:09 +00:00
CHANGELOG.md chore: bump version to 0.4.0 and update changelog 2021-04-23 09:55:28 +02:00
Cargo.lock chore: bump version to 0.4.0 and update changelog 2021-04-23 09:55:28 +02:00
Cargo.toml chore: bump version to 0.4.0 and update changelog 2021-04-23 09:55:28 +02:00
LICENSE Add LICENSE 2019-02-05 10:33:05 +00:00
README.md feat: add healthcheck endpoint 2021-04-19 11:45:24 +02:00
config.toml.sample improve documentation 2020-04-06 22:50:32 +02:00

README.md

peshming

It's a prometheus exporter pinging hosts in the background. It's been inspired by meshping, but instead of managing targets using a redis db this is using a simple config file. In addition, this tool allows to set a ping frequency per target.

The name peshming is intended as a placeholder until someone comes up with something better.

Usage:

$ peshming --help
peshming 0.2.3
Jan Christian Grünhage <jan.christian@gruenhage.xyz>
Pings configured hosts in a configurable intervals and exposes metrics for prometheus.

USAGE:
    peshming [FLAGS] <config>

FLAGS:
    -h, --help       Prints help information
    -v, --verbose    Be verbose (you can add this up to 4 times for more logs).
                     By default, only errors are logged, so no output is a good thing.
    -V, --version    Prints version information

ARGS:
    <config>    Set config file

For configuration options, see the included sample config file.

Endpoints:

There's two endpoints available:

  • /metrics, which serves the metrics
  • /health, which should always return a 200 status code