MAX_CREATES_PER_MINUTE results in dropping new metrics

tux_tina

According to carbon.conf any metrics received in excess of MAX_CREATES_PER_MINUTE value will be silently dropped, and the whisper file will not be created until such point as a subsequent metric is received and fits within the defined rate limit I'm wondering why not putting them in cache (similar to MAX_UPDATES_PER_SECOND behaviour) instead?

Originally asked by mhdwrk on Stack Exchange (stackoverflow) (CC BY-SA 3.0).

uphilltech

Good thread on this — worth a read before you pay anyone to build it.

Discussion: https://stackoverflow.com/questions/42492166/max-creates-per-minute-results-in-dropping-new-metrics.

Want it set up for you? UphillTech.