Metric is_error changed the type of response codes

[#1]

Hi guys,

In the documentation, about the metric is_error you have:

"The is_error metric defines any message that results in an HTTP 4xx or 5xx HTTP status code"

However, since the beginning of April it seems that you changed the response codes associated with the metric is_error. In the example below, for the code 302 it became classified as error and not success.

Is there any reason for this?

.../environments/prod/stats/response_status_code?"select=sum(message_count),sum(is_error)&timeRange=03/29/2015%2000:00~03/30/2015%2000:00&timeUnit=day"


"dimensions" : [ {
  "metrics" : [ {
	"name" : "sum(is_error)",
	"values" : [ {
	  "timestamp" : 1427587200000,
	  "value" : "0.0"
	} ]
  }, {
	"name" : "sum(message_count)",
	"values" : [ {
	  "timestamp" : 1427587200000,
	  "value" : "21500.0"
	} ]
  } ],
  "name" : "302"
} ]


.../environments/prod/stats/response_status_code?"select=sum(message_count),sum(is_error)&timeRange=04/01/2015%2000:00~04/02/2015%2000:00&timeUnit=day"


"dimensions" : [ {
  "metrics" : [ {
	"name" : "sum(is_error)",
	"values" : [ {
	  "timestamp" : 1427846400000,
	  "value" : "11900.0"
	} ]
  }, {
	"name" : "sum(message_count)",
	"values" : [ {
	  "timestamp" : 1427846400000,
	  "value" : "11900.0"
	} ]
  } ],
  "name" : "302"
} ]

Thanks.