2011/Designing Error Aggregation Systems

From Open Source Bridge Wiki
Jump to: navigation, search

So often we’re solely focused on the performance of our production systems. When disaster strikes, your team needs to know when error conditions begin, where they’re coming from, frequency, and an indication of the last time they occurred. Parsing logs isn’t fast enough, and email can’t keep up or preserve metadata.

Speaker: Gavin McQuillan

Return to this session's details

Contributed notes


Designing Error Aggregation Systems Slides: [1]