envoyproxy/envoy

Allow option to not emit statsd metrics when reporting a `0` value

Open

#6.205 geöffnet am 7. März 2019

Auf GitHub ansehen
 (4 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)C++ (5.373 Forks)batch import
enhancementhelp wanted

Repository-Metriken

Stars
 (27.997 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 8T) (378 gemergte PRs in 30 T)

Beschreibung

We store the statsd metrics envoy emits in a SAAS monitoring tool that charges us based on the number of measurements we store at a particular reporting interval. Some of the metrics we are recording are consistently 0, with occasional spikes when something happens. Here's an example:

image 2019-03-07 at 11 54 16 am

I can see the value in using a 0 value to report "nothing is happening", but our monitoring bill has doubled as a result of adopting envoy(!), and continues to grow as we add more clusters, so we'd like to save some money by not recording measurements we can mostly infer from an absence of data.

That said, the zero values were very helpful when were spiking into adopting envoy, as it allowed us to see which metrics we could expect from envoy. Maybe this should be a configuration option in the StatsMatcher proto?

Contributor Guide