about a problem then you have already failed at least twice • The right quan%ty • Filtering – see the right picture • Document changes to your baselines
• Not only at the top level • Component rate limi%ng • Rate limi%ng should be dynamic • Rate limi%ng can be par%%oned • Clients should be part of the contract • Rate limi%ng is aLer all handshaking • Handshaking: within the protocol or out of band
The opera%onal one • The customers one No maXer how sophis%cated is our monitoring infrastructure issues no%fied by customers are at the end the most important ones as they impact their experience directly and are oLen discovering unknown bugs. Freeing up the team as much as possible from the overhead of the first type gives more %me to focus on the issues of the product itself.