update docs

Author: mitchellhenke

README.md

@@ -38,13 +38,22 @@ For optional settings check the [docs](https://hexdocs.pm/sentry/readme.html).
 
 ### Setup with Plug or Phoenix
 
-In your router add the following lines:
+In your Plug.Router or Phoenix.Router, add the following lines:
 
 ```elixir
 use Plug.ErrorHandler
 use Sentry.Plug
 ```
 
+If you are using Phoenix, you can also include [Sentry.Phoenix.Endpoint](https://hexdocs.pm/sentry/Sentry.Phoenix.Endpoint.html) in your Endpoint. This module captures errors occurring in the Phoenix pipeline before the request reaches the Router:
+
+```elixir
+use Phoenix.Endpoint, otp_app: :my_app
+use Sentry.Phoenix.Endpoint
+```
+
+More information on why this may be necessary can be found here: https://github.com/getsentry/sentry-elixir/issues/229 and https://github.com/phoenixframework/phoenix/issues/2791
+
 ### Capture All Exceptions
 
 This library comes with an extension to capture all error messages that the Plug handler might not.  This is based on the Erlang [error_logger](http://erlang.org/doc/man/error_logger.html).

docs/index.rst

@@ -115,7 +115,7 @@ Filtering Events
 If you would like to prevent certain exceptions, the ``:filter`` configuration option
 allows you to implement the ``Sentry.EventFilter`` behaviour.  The first argument is the
 exception to be sent, and the second is the source of the event.  ``Sentry.Plug``
-will have a source of ``:plug``, and ``Sentry.Logger`` will have a source of ``:logger``.
+will have a source of ``:plug``, ``Sentry.Logger`` will have a source of ``:logger``, and ``Sentry.Phoenix.Endpoint`` will have a source of ``:endpoint``.
 If an exception does not come from either of those sources, the source will be nil
 unless the ``:event_source`` option is passed to ``Sentry.capture_exception/2``
 

lib/sentry.ex

@@ -54,7 +54,7 @@ defmodule Sentry do
   If you would like to prevent certain exceptions, the `:filter` configuration option
   allows you to implement the `Sentry.EventFilter` behaviour.  The first argument is the
   exception to be sent, and the second is the source of the event.  `Sentry.Plug`
-  will have a source of `:plug`, and `Sentry.Logger` will have a source of `:logger`.
+  will have a source of `:plug`, `Sentry.Logger` will have a source of `:logger`, and `Sentry.Phoenix.Endpoint` will have a source of `:endpoint`.
   If an exception does not come from either of those sources, the source will be nil
   unless the `:event_source` option is passed to `Sentry.capture_exception/2`
 

lib/sentry/phoenix_endpoint.ex

@@ -1,8 +1,10 @@
 defmodule Sentry.Phoenix.Endpoint do
   @moduledoc """
-  Provides basic functionality to handle errors in a Phoenix Endpoint. Errors occurring within a Phoenix request before it reaches the Router will not be captured by `Sentry.Plug` due to the internal workings of Phoenix.
+  Provides basic functionality to handle errors in a Phoenix Endpoint. Errors occurring within a Phoenix request before it reaches the Router will not be captured by `Sentry.Plug` due to the internal functionality of Phoenix.
 
-  For more information, see https://github.com/getsentry/sentry-elixir/issues/229.
+  It is recommended to include `Sentry.Phoenix.Endpoint` in your Phoenix app if you would like to receive errors occurring in the previously mentioned circumstances.
+
+  For more information, see https://github.com/getsentry/sentry-elixir/issues/229 and https://github.com/phoenixframework/phoenix/issues/2791.
 
 
   #### Usage