-
Notifications
You must be signed in to change notification settings - Fork 670
Expose metrics #2535
Comments
'Flow misses' is also interesting if it is increasing rapidly. |
Good point! |
@carlpett we're going to be working on this as a matter of priority for kubecon (~4 weeks from now) 😄 |
Excellent! 😆 |
I have done a bit of this, in #2547. Some points to note:
|
These are the specific metrics implemented in #2547: "weave_connections", "Number of peer-to-peer connections." The last two are struck through because they were subsequently removed from |
Following discussions on Slack:
We'd like to be able to monitor our Weave Net, so that we know that all is well. Preferrably, we'd like this exposed as a prometheus metrics endpoint.
Some suggested metrics:
expose
allocations?)It would be interesting to maintain the source/dest information in the last two, but from a prometheus perspective it might lead to generating too many timeseries?
The text was updated successfully, but these errors were encountered: