In the post-processing step (logstash?) identify where the error comes from at a high level (such as extension name or ResourceLoader module name) and ping graphite so it can show error frequency graphs for those error sources.
For reference, here is how NavigationTiming adds its numbers to graphite: puppet manifest, upstart script, python script