This episode is for members only
Sign up to access "Build An Uptime Monitor with Inertia" right now.
Get started
Already a member? Sign in to continue
Playing
43. Recovery notification bug
Episodes
01. Introduction
02. Sites
03. Endpoints
09. Setting up endpoints
4m 23s
0%
10. Enum endpoint frequencies
3m 50s
0%
11. Creating the endpoint form
12m 58s
0%
12. Storing an endpoint
7m 21s
0%
13. Validating and authorizing endpoint stores
7m 6s
0%
14. Normalizing the endpoint location
6m 4s
0%
15. Displaying endpoints
6m 22s
0%
16. Deleting endpoints
6m 21s
0%
17. Toggling inline editing for endpoints
5m 12s
0%
18. Applying a watcher to the endpoint form
5m 31s
0%
19. Storing endpoint edits
8m 56s
0%
04. Checking endpoints
20. Determining endpoints to check
2m 57s
0%
21. Creating a job to perform a check
3m 21s
0%
22. Making an HTTP request
3m 39s
0%
23. Scheduling checks every second
4m 27s
0%
24. Setting up the check relationship
3m 14s
0%
25. Updating the job
2m 10s
0%
26. Showing the last status
12m 50s
0%
27. Expanded list of checks
14m 10s
0%
28. The response body modal
2m 49s
0%
29. Authorizing the endpoint details
2m 27s
0%
30. Calculating uptime for endpoints
8m 29s
0%
06. Email notifications
07. Downtime notifications
Transcript
00:00
You may have spotted this bug if you've been following along but if we add an endpoint and it's initially successful, our recovery email is actually going to get triggered. So I've got everything up and running here in the terminal, I've got my email client open and we're going to go ahead and add an endpoint here to see what happens.
00:18
So let's actually delete some of these just so we can choose one that we've already got in this list. So I'm going to go ahead and add in the pro endpoint and I'm just going to wait for them 10 seconds to kick in and actually show that this was successful and what we should get through is an email saying that it is recovered and there it is. So pro has recovered, not good,
00:42
that's not what we want to see when we first add a successful endpoint. So if we go over to our check observer, let's just check what we've done here. Now we run this or more appropriately we dispatch this event. If the check was successful, which we have in that case because it's a valid endpoint and it's fine, the previous check was
01:03
not successful. Now we don't have a previous check but this will return null to us because we are assuming that there may not be a previous check and when we access this is successful method on here it's going to return us a null value. But what we're doing here is saying that the endpoint checks count needs to be greater than one. What we can actually say here is that the endpoint
01:26
checks count doesn't equal one because that is when we freshly add in a endpoint. So let's get rid of that and let's try this out. So once again let's just close this off for a little bit of clarity. We're going to stop our queue and restart it and let's go over and just give this a refresh. So I'm going to delete this endpoint, I'm going to re-add it in here and I'm just going to wait
01:48
for 10 seconds and we should not now see an email triggered. Okay so we're now onto a 200 status that hasn't triggered a recovered email. Now this was the one from before so let's get rid of that and let's just go through the whole process again of setting this up so it fails and then recovers. So you can see here ABC went down because I just changed it just as the check happened
02:10
and now we're going to recover it and actually make sure that that email comes in. So let's hit done give that a few seconds to do its thing and sure enough pro has recovered. So there we go a tiny mistake there in the way that we set up the check on the count. We don't want to trigger this if the only check that we have created was successful.
44 episodes•4 hrs 59 mins•2 years ago
Overview
Ready to dive into Inertia? Let's build a real-world app with Laravel, Inertia and Vue! If you're already working with Inertia, you'll pick up some tips and techniques for future projects.
This uptime monitor allows you to create and switch between sites, then add endpoints to monitor with frequency intervals. Using the power of scheduling and queues, it'll automatically alert the email addresses you've added via the UI when an endpoint goes down.
In this course, you'll learn to:
- Build a real app from scratch with Inertia
- Work with Laravel queues
- Perform actions on models at user-defined intervals
- Work with sub-minute schedules in Laravel
- Send out channel notifications with Laravel
- Use API resources to simplify Inertia data
- Organise apps with events and observers
- Create modals in Vue
- Perform inline editing with Inertia forms
Alex Garrett-Smith
Hey, I'm the founder of Codecourse!
Episode discussion
No comments, yet. Be the first!