Improve statsdstats logging for pulled atoms
1. remove old statscompanion counters 2. add outgoing binder call fail counts 3. Add additional pull failure cases a. No pull uid provider (If a config doesn't register properly) b. Puller not found - either because it was not registered or because the client did not specify the correct uids 4. Make metrics own logging pull delays - these were getting overcounted since both the PullerManager and ValueMetricProducer were logging pull delays. 5. Move noteEmptyPull to StatsPuller for more uniform logging, instead of it just being logged in value metric producer. Test: m statsd Bug: 154056912 Change-Id: Ia373003905ee44d3b7b37b2bfa1e1d6268250070
Loading
Please register or sign in to comment