apps/metricator
2
0
Fork 0
Code Issues 5 Pull Requests Packages Projects Releases Wiki Activity
Prometheus metrics proxy for your classic NMS.
33 Commits 1 Branch 5 Tags 134 KiB
Go 91.4%
Shell 3.6%
Makefile 3.1%
Dockerfile 1.9%
cdbb3b7089
Go to file
Stanislav N. aka pztrn cdbb3b7089
Add possibility to format metricator client output. 
Closes #5.
2020-12-24 23:15:56 +05:00
cmd Add possibility to format metricator client output. 2020-12-24 23:15:56 +05:00
docs Documentation improvement. 2020-12-23 21:33:39 +05:00
internal The very basic metricator-client and package. 2020-12-24 23:06:13 +05:00
pkg The very basic metricator-client and package. 2020-12-24 23:06:13 +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 Rethink how metricator will work, golangci-lint and gitlab ci configs. 2020-11-29 03:22:39 +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 improvements. 2020-12-24 13:48:00 +05:00
CHANGELOG.md Documentation. 2020-12-23 21:13:56 +05:00
Dockerfile Fix binary path for docker building. 2020-12-23 20:28:24 +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
Makefile The very basic metricator-client and package. 2020-12-24 23:06:13 +05:00
metricator.example.yaml Documentation. 2020-12-23 21:13:56 +05:00
README.md Rethink how metricator will work, golangci-lint and gitlab ci configs. 2020-11-29 03:22:39 +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.