-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ipfs namespace is now being provided to prometheus #6643
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor breaking change but I'm fine with it as long as you make sure to upgrade the Prometheus dashboards (and migrate any data if necessary).
core/corehttp/metrics.go
Outdated
Subsystem: "http", | ||
ConstLabels: prometheus.Labels{"handler": handlerName}, | ||
Objectives: map[float64]float64{0.5: 0.05, 0.9: 0.01, 0.99: 0.001}, | ||
} | ||
|
||
reqCnt := prometheus.NewCounterVec( | ||
prometheus.CounterOpts{ | ||
Namespace: opts.Namespace, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't we keep this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ahh yes we should.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nudge @lanzafame
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
@olizilla @Stebalien fixed. thanks for the nudge |
…mespace ipfs namespace is now being provided to prometheus This commit was moved from ipfs/kubo@4a10220
This fixes what was a rather confusing issue in prometheus where the
http_response_size_bytes
metrics was confused to be coming from nginx but was actually from ipfs.