8 Commits

Author	SHA1	Message	Date
Janek Łukaszewicz	1dda3d8dfc	kube-proxy: change buckets used by NetworkProgrammingLatency ... refs https://github.com/kubernetes/perf-tests/issues/640 We have too fine buckets granularity for lower latencies, at cost of the higher latecies (7+ minutes). This is causing spikes in SLI calculated based on that metrics. I don't have strong opinion about actual values - those seemed to be better matching our need. But let's have discussion about them. Values: 0.015 s 0.030 s 0.060 s 0.120 s 0.240 s 0.480 s 0.960 s 1.920 s 3.840 s 7.680 s 15.360 s 30.720 s 61.440 s 122.880 s 245.760 s 491.520 s 983.040 s 1966.080 s 3932.160 s 7864.320 s	2019-07-16 16:43:19 +02:00
Casey Callendrello	017f57a6b0	proxy: add some useful metrics ... This adds some useful metrics around pending changes and last successful sync time. The goal is for administrators to be able to alert on proxies that, for whatever reason, are quite stale. Signed-off-by: Casey Callendrello <cdc@redhat.com>	2019-05-07 14:21:13 +02:00
danielqsj	10ab3fb832	clean the deprecated metrics which introduced recently	2019-03-06 15:23:46 +08:00
danielqsj	f7b437cae0	convert latency in mertics name to duration	2019-02-22 21:40:13 +08:00
Matt Matejczyk	7141ece4bf	Start exporting the in-cluster network programming latency metric.	2019-02-12 08:09:59 +01:00
danielqsj	1fb91a7206	Mark deprecated in related proxy metrics	2019-01-08 13:15:25 +08:00
danielqsj	8975e62254	Change proxy metrics to conform guideline	2018-12-26 17:25:10 +08:00
m1093782566	dab9b84b67	add proxy metrics in app level	2017-10-16 21:10:51 +08:00