apps
/
metricator
2
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity
Prometheus metrics proxy for your classic NMS.
44 Commits 1 Branch 5 Tags 189 KiB
Go 91.4%
Shell 3.6%
Makefile 3.1%
Dockerfile 1.9%
Go to file
Stanislav Nikitin 26ce90bb84
Linting fixes. 		2021-11-21 14:45:09 +05:00
cmd Linting fixes. 2021-11-21 14:45:09 +05:00
docs Documentation update and linting fix. 2020-12-24 23:33:24 +05:00
internal Linting fixes. 2021-11-21 14:45:09 +05:00
pkg Linting fixes. 2021-11-21 14:45:09 +05:00
scripts Version 0.2.0 and build fix. 2021-02-19 19:43:52 +05:00
.drone.yml Add Drone configuration. 2021-11-21 14:12:09 +05:00
.gitignore Add Drone configuration. 2021-11-21 14:12:09 +05:00
.gitlab-ci.yml Add forgotten docker image name and move lint-test image name into vars. 2020-12-23 20:08:47 +05:00
.golangci.yml Linting fixes. 2021-11-21 14:45:09 +05:00
CHANGELOG.md Documentation. 2020-12-23 21:13:56 +05:00
Dockerfile Add metricator-client to docker image. 2020-12-24 23:17:38 +05:00
Makefile Fix errors when building something with make. 2021-02-19 19:18:10 +05:00
README.md Rethink how metricator will work, golangci-lint and gitlab ci configs. 2020-11-29 03:22:39 +05:00
VERSION Version 0.2.0 and build fix. 2021-02-19 19:43:52 +05:00
go.mod Rethink how metricator will work, golangci-lint and gitlab ci configs. 2020-11-29 03:22:39 +05:00
go.sum Rethink how metricator will work, golangci-lint and gitlab ci configs. 2020-11-29 03:22:39 +05:00
metricator.example.yaml Documentation. 2020-12-23 21:13:56 +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.