I would also like to note that status_code label can lead to 'overflow'. While set of values of this label is definitely finite it's still can be large. Prometheus treats each label set as separate time series.
Likely there is also usability issue - imagine you want to graph all successful replies then you have to use regex matches. So maybe introduce status_class label and make status_code optional?
See #3 for discussion.