Crates.io | vigil-reporter |
lib.rs | vigil-reporter |
version | 1.3.0 |
source | src |
created_at | 2018-01-11 08:12:59.09672 |
updated_at | 2023-03-29 16:51:21.092897 |
description | Vigil Reporter for Rust. Used in pair with Vigil, the Microservices Status Page. |
homepage | https://github.com/valeriansaliou/rs-vigil-reporter |
repository | https://github.com/valeriansaliou/rs-vigil-reporter.git |
max_upload_size | |
id | 46375 |
size | 15,834 |
Vigil Reporter for Rust. Used in pair with Vigil, the Microservices Status Page.
Vigil Reporter is used to actively submit health information to Vigil from your apps. Apps are best monitored via application probes, which are able to report detailed system information such as CPU and RAM load. This lets Vigil show if an application host system is under high load.
đđē Crafted in Budapest, Hungary.
đ You use vigil-reporter and you want to be listed there? Contact me.
Include vigil-reporter
in your Cargo.toml
dependencies:
[dependencies]
vigil-reporter = "1.0"
vigil-reporter
can be instantiated as such:
extern crate vigil_reporter;
use std::time::Duration;
use vigil_reporter::Reporter;
// Build reporter
// `page_url` + `reporter_token` from Vigil `config.cfg`
let reporter = Reporter::new("https://status.example.com", "YOUR_TOKEN_SECRET")
.probe_id("relay") // Probe ID containing the parent Node for Replica
.node_id("socket-client") // Node ID containing Replica
.replica_id("192.168.1.10") // Unique Replica ID for instance (ie. your IP on the LAN)
.interval(Duration::from_secs(30)) // Reporting interval (in seconds; defaults to 30 seconds if not set)
.build();
// Run reporter (starts reporting)
reporter.run();
âšī¸ Wondering what Vigil is? Check out valeriansaliou/vigil.