Send better stack traces

Prior to this commit, the stack trace sent to Sentry would include references
to all the FireGento Logger code plus this extension's logger. This made it
harder to quickly determine where the actual error/exception occurred.

So now we simply attempt to "rewind" the stack trace to the point where the
error/exception occurred.  And if for any reason we can't, we'll just use the
original functionality.

Author: colinodell

app/code/community/Hackathon/LoggerSentry/Model/Sentry.php

@@ -94,8 +94,10 @@ protected function _write($eventObj)
 
             $this->_addUserContext($eventObj);
 
+            $stack = $this->_getStackTrace($event);
+
             $this->_sentryClient->captureMessage(
-                $event['message'], array(), $this->_priorityToLevelMapping[$priority], true, $additional
+                $event['message'], array(), $this->_priorityToLevelMapping[$priority], $stack, $additional
             );
 
         } catch (Exception $e) {
@@ -161,6 +163,29 @@ protected function _addUserContext($eventObj)
         }
     }
 
+    /**
+     * @param array $event
+     *
+     * @return array
+     */
+    protected function _getStackTrace($event)
+    {
+        $stack = debug_backtrace();
+        // Remove the call to this _getStackTrace() function
+        array_shift($stack);
+
+        if (isset($event['file']) && isset($event['line'])) {
+            // "Unwind" the stack until we find where this was actually triggered from
+            foreach ($stack as $i => $item) {
+                if ($item['line'] === $event['line'] && strpos($item['file'], $event['file']) !== false) {
+                    return array_slice($stack, $i);
+                }
+            }
+        }
+
+        return $stack;
+    }
+
     /**
      * Satisfy newer Zend Framework
      *