Merge pull request #382 from hubblo-org/369-json-file-output-format

369 json file output format

Cargo.toml

@@ -32,6 +32,7 @@ hyper = { version = "0.14", features = ["full"], optional = true }
 tokio = { version = "1.26.0", features = ["full"], optional = true}
 sysinfo = { version = "0.28.3"}
 isahc = { version = "1.7.2", optional = true }
+ctrlc = { version = "3.4", features = [ "termination" ] }
 
 [target.'cfg(target_os="linux")'.dependencies]
 procfs = { version = "0.15.0" }

docs_src/references/exporter-json.md

@@ -56,4 +56,4 @@ As always exporter's options can be displayed with `-h`:
       -h, --help
               Print help
 
-Metrics provided Scaphandre are documented [here](references/metrics.md).
+Metrics provided Scaphandre are documented [here](metrics.md).

docs_src/references/exporter-prometheus.md

@@ -34,4 +34,4 @@ With default options values, the metrics are exposed on http://localhost:8080/me
 Use -q or --qemu option if you are running scaphandre on a hypervisor. In that case a label with the vm name will be added to all `qemu-system*` processes.
 This will allow to easily create charts consumption for each vm and defined which one is the top contributor.
 
-Metrics provided Scaphandre are documented [here](references/metrics.md).
+Metrics provided Scaphandre are documented [here](metrics.md).

docs_src/references/exporter-riemann.md

@@ -87,7 +87,7 @@ As a reference here is a Riemann configuration:
 
 ## Metrics exposed
 
-Metrics provided Scaphandre are documented [here](references/metrics.md).
+Metrics provided Scaphandre are documented [here](metrics.md).
 
 There is only one exception about `process_power_consumption_microwatts` each process has a service name `process_power_consumption_microwatts_pid_exe`.
 

docs_src/references/exporter-warp10.md

@@ -34,4 +34,4 @@ With default options values, the metrics are sent to http://localhost:8080 every
 Use -q or --qemu option if you are running scaphandre on a hypervisor. In that case a label with the vm name will be added to all `qemu-system*` processes.
 This will allow to easily create charts consumption for each vm and defined which one is the top contributor.
 
-Metrics provided Scaphandre are documented [here](references/metrics.md). 
+Metrics provided Scaphandre are documented [here](metrics.md).