fbegyn / tc_exporter Goto Github PK
View Code? Open in Web Editor NEWPrometheus exporter for TC statistics
License: MIT License
tc_exporter's People
Contributors
Stargazers
Watchers
Forkers
sgnsys3tc_exporter's Issues
replace arg parsing with config file
Service curve collector not working
Currently the service curve is not working. Tests are failing with
=== RUN TestServiceCurveCollector
=== RUN TestServiceCurveCollector/dummy01
TestServiceCurveCollector/dummy01: class_test.go:116: failed to add HFSC qdisc: Hfsc: missing argument
=== RUN TestServiceCurveCollector/dummy1000
TestServiceCurveCollector/dummy1000: class_test.go:116: failed to add HFSC qdisc: Hfsc: missing argument
--- FAIL: TestServiceCurveCollector (0.05s)
--- FAIL: TestServiceCurveCollector/dummy01 (0.03s)
--- FAIL: TestServiceCurveCollector/dummy1000 (0.03s)
Need to look into this more, but it seems HFSC testing is not completely implemented in https://github.com/florianl/go-tc , so first verifying that the HFSC can correctly be added and work.
unify data fetched from netlink api
Does not work on Debian 12
Hi
Upgrade to Debian 12 broke the tc_exporter. The problem is with finding the network interfaces.
ts=2023-06-11T11:12:37.352021706Z version=v0.7.0 caller=main.go:74 msg="failed to get interfaces from ns" err="incorrect size, want: 184 or 192" netns=default
I tried to upgrade the netlink library, but it didn't help
johan@shaper:~/tc_exporter$ git diff go.mod
diff --git a/go.mod b/go.mod
index 5ca06b5..25e1d24 100644
--- a/go.mod
+++ b/go.mod
@@ -6,11 +6,11 @@ require (
github.com/florianl/go-tc v0.1.1-0.20200404145214-71dd2225291c
github.com/go-kit/kit v0.10.0
github.com/jsimonetti/rtnetlink v0.0.0-20200319143528-d89fb9e42094
- github.com/mdlayher/netlink v1.1.0
+ github.com/mdlayher/netlink v1.7.2
github.com/mdlayher/promtest v0.0.0-20190902162024-2b6f8ce579e3
github.com/prometheus/client_golang v1.5.0
github.com/spf13/viper v1.6.2
- golang.org/x/sys v0.0.0-20200320181252-af34d8274f85
+ golang.org/x/sys v0.7.0
gopkg.in/alecthomas/kingpin.v2 v2.2.6
gopkg.in/yaml.v2 v2.2.8 // indirect
)
export network namespaces
It would be good to export the namespaces with the metrics. I'd suggest making an additional label namespace and storing the namespace in there. This way we only need 1 instance on a system with multiple namespaces instead of an exporter for every namespace.
enable prometheus exporting by default
Would it not make sense to enable exporting metrics with a prometheus endpoint by default? And then have the influx component be opt-in.
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.