You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/posts/170723-monitor-flask-apps.markdown
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -160,13 +160,20 @@ command as follows:
160
160
python app.py
161
161
```
162
162
163
-
We can see the error because we are testing our application locally,
164
-
but what happens when our application is deployed and a user gets the
165
-
error? They will typically quit out of frustration and you will never
166
-
know what happened unless you add some error tracking and application
167
-
monitoring.
163
+
The Flask development server should start up and display a few lines
164
+
of output.
168
165
169
-
We'll now modify our code to add Rollbar to catch and report those
166
+
<imgsrc="/img/170723-monitor-flask-apps/python-app-py.png"width="100%"class="technical-diagram img-rounded"style="border:1pxsolid#ccc"alt="Run the Flask development server locally.">
167
+
168
+
**Test app out... happy path, error 404 and error 500.***
169
+
170
+
The error is obvious to us because we are testing the application locally,
171
+
but what happens when the application is deployed and a user gets the
172
+
error in their own web browser? They will typically quit out of
173
+
frustration and you will never know what happened unless you add some
174
+
error tracking and application monitoring.
175
+
176
+
We will now modify our code to add Rollbar to catch and report those
0 commit comments