Handle slow/nil Graphite metrics

Sometimes graphite is slow and will return null as the datapoint value
for a given timestamp because either the true value is null or it is
being buffered in the carbon cache and hasn't been written yet. By mapping
the array values and restricting ourselves to actual real values we can
obtain a much better alarm state and prevent an error