Connect Tornado to Bugsink
When a Tornado request fails, Bugsink shows you the exception, the application frame that raised it, and the HTTP request that reached the handler.
This guide covers the initial setup and Tornado’s automatic capture of unhandled request-handler exceptions. You’ll connect an existing application, then make one request fail to confirm that it reaches Bugsink.
To follow along, create a Bugsink project and copy its DSN. The quickstart guide shows where to find it.
Install the SDK
Install the open-source Sentry SDK with its Tornado integration in the environment your application uses. Bugsink accepts the Sentry event protocol, so the SDK can send events directly to your Bugsink project.
python -m pip install --upgrade "sentry-sdk[tornado]"python -m pip install --upgrade "sentry-sdk[tornado]"
Configure Tornado
Import the SDK and Tornado integration where you create the application:
import sentry_sdk import tornado.web from sentry_sdk.integrations.tornado import TornadoIntegrationimport sentry_sdk import tornado.web from sentry_sdk.integrations.tornado import TornadoIntegration
Initialize the SDK before creating the Application. Reading the DSN from the
environment keeps it out of source control:
sentry_sdk.init( dsn=os.environ["SENTRY_DSN"], integrations=[TornadoIntegration()], )sentry_sdk.init( dsn=os.environ["SENTRY_DSN"], integrations=[TornadoIntegration()], )
Set SENTRY_DSN in the environment where the application runs:
export SENTRY_DSN=https://key@bugsink.example/1export SENTRY_DSN=https://key@bugsink.example/1
Trigger an unhandled exception
If a request handler raises an exception and does not catch it, the integration reports it automatically. There is no SDK call inside the handler. To verify the setup, this checkout handler raises an exception for an unknown product:
class CheckoutHandler(tornado.web.RequestHandler): def get(self, sku): try: product = inventory[sku] except KeyError: raise ProductNotFound(f"Product {sku} is not in inventory") from None self.write({"reserved": product["name"]})class CheckoutHandler(tornado.web.RequestHandler): def get(self, sku): try: product = inventory[sku] except KeyError: raise ProductNotFound(f"Product {sku} is not in inventory") from None self.write({"reserved": product["name"]})
The application maps the handler to /checkout/<sku>:
def make_app(): return tornado.web.Application( [ (r"/", InventoryHandler), (r"/checkout/([^/]+)", CheckoutHandler), ] )def make_app(): return tornado.web.Application( [ (r"/", InventoryHandler), (r"/checkout/([^/]+)", CheckoutHandler), ] )
Start the application as usual, then request a product that does not exist:
python app.py :::bash curl http://127.0.0.1:8080/checkout/tornado-missingpython app.py :::bash curl http://127.0.0.1:8080/checkout/tornado-missing
Tornado returns an HTTP 500 response and the integration reports the exception.
See the error in Bugsink
Open your Bugsink project and select the new ProductNotFound issue. Its event
points to the failing line in the handler and includes the GET request.
ProductNotFound
That’s it: unhandled Tornado request-handler exceptions will now be reported to Bugsink.
The integration runs around Tornado’s request handling, so your handlers stay ordinary application code. An unhandled exception includes its Python stack, the application source frame, and the HTTP request that reached the handler.
If your application catches an exception itself, report it explicitly with
capture_exception().
