apps
/
metricator
2
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity
Prometheus metrics proxy for your classic NMS.
2 Commits 1 Branch 5 Tags 189 KiB
Go 91.4%
Shell 3.6%
Makefile 3.1%
Dockerfile 1.9%
Go to file
Stanislav Nikitin e679fecf6e
Correctly set version info when building, fixed build script and added headers for apps endpoints. 		2020-11-28 23:46:24 +05:00
cmd/metricatord Initial commit. 2020-11-28 23:34:20 +05:00
docs Initial commit. 2020-11-28 23:34:20 +05:00
internal Correctly set version info when building, fixed build script and added headers for apps endpoints. 2020-11-28 23:46:24 +05:00
scripts Correctly set version info when building, fixed build script and added headers for apps endpoints. 2020-11-28 23:46:24 +05:00
.gitignore Initial commit. 2020-11-28 23:34:20 +05:00
Makefile Correctly set version info when building, fixed build script and added headers for apps endpoints. 2020-11-28 23:46:24 +05:00
README.md Initial commit. 2020-11-28 23:34:20 +05:00
go.mod Initial commit. 2020-11-28 23:34:20 +05:00
go.sum Initial commit. 2020-11-28 23:34:20 +05:00
metricator.example.yaml Initial commit. 2020-11-28 23:34:20 +05:00

README.md

Metricator

Simple proxy between prometheus-powered application and your NMS.

Why

I'm using NetXMS to monitor all of my systems. Many things I use exports metrics in prometheus format which can be utilized by custom parsing script. But I've encounter a performance problem when I need to monitor 30 metrics - parsing script will make 30 requests to prometheus endpoint which might affect performance.

Metricator will issue only one request and cache data in memory between them. Also it will expose HTTP API to get single metric which can be easily utilized with any NMS.

Caveats

  • No authorization. DO NOT expose Metricator to wild world!

Installation

TBW

Configuration

TBW

Documentation

Check docs directory.