Build An Uptime Monitor with Inertia

Sign in Get started

This episode is for members only

Sign up to access "Build An Uptime Monitor with Inertia" right now.

Already a member? Sign in to continue

Playing

23. Scheduling checks every second

Episodes

0%

Your progress

Total: 4h 59m
Played: 0m
Remaining: 4h 59m

Join or sign in to track your progress

01. Introduction

01. Introduction and demo

02. A fresh Inertia project

02. Sites

03. Site and dashboard setup

04. Building the site selector dropdown

05. Making use of API resources

06. Setting the default site

07. Setting up Vue modals

08. Creating a site

03. Endpoints

09. Setting up endpoints

10. Enum endpoint frequencies

11. Creating the endpoint form

12. Storing an endpoint

13. Validating and authorizing endpoint stores

14. Normalizing the endpoint location

15. Displaying endpoints

16. Deleting endpoints

17. Toggling inline editing for endpoints

18. Applying a watcher to the endpoint form

19. Storing endpoint edits

04. Checking endpoints

20. Determining endpoints to check

21. Creating a job to perform a check

22. Making an HTTP request

23. Scheduling checks every second

24. Setting up the check relationship

25. Updating the job

26. Showing the last status

27. Expanded list of checks

28. The response body modal

29. Authorizing the endpoint details

30. Calculating uptime for endpoints

05. Queuing

31. Setting up queues

32. Queuing the endpoint check

06. Email notifications

33. Setting up email in Laravel

34. Site model email notification storage

35. Adding email addresses via the UI

36. Listing and deleting email addresses

07. Downtime notifications

37. Observing when to notify

38. Creating an endpoint down notification

39. Creating an endpoint recovery notification

40. Making the emails a bit friendlier

08. Extras

41. Deleting sites

42. Eager loading

43. Recovery notification bug

44. No sites fix and placeholder

Transcript

00:00

Up until now, we've been manually running the command performChecks. Now, obviously, that's not what we want to do. We want to schedule this to be run at a certain frequency or an interval.

00:12

Now, unfortunately, within Laravel, the minimum that we can run a scheduled command at is every minute. So let's look at how we would do that first of all, and then we're going to look at an alternative solution. So we're going to come over to our console kernel here, which is where we can schedule specific commands to be run. For example, we can schedule this inspire command, which outputs a quote hourly and so on and so forth.

00:39

Now, our command is called, if we just head up here, checks perform. Let's grab the name of that and just replace this out in here. Now, we can do this every minute. So that works for some things.

00:52

We can do it at any interval we want. The only problem is we don't have any way to do this every second, which is a problem. Let's discuss why that is. Now, our next check is extremely specific because the frequency that we're working out here is within seconds.

01:09

So we could technically run this every minute and it would run some of these, but we would get some sort of overlap at some point where some of these are not run or some of them are run too frequently. So what we really want to do is make this every second. We want to run this every single second.

01:27

And then when we have an exact match within the minutes and the seconds here, that's going to then increment. And then the next time this runs, it's going to work really nicely. So to get around this, we're going to go ahead and use the Laravel short schedule package. Let's go ahead and install this.

01:42

It's really, really easy to get set up with. We just need to go ahead and require this in and then add a method to our kernel here. So we're going to go ahead and pull that in and then we're going to go ahead and get rid of this. We're going to come down here and we're going to create out a protected method in here called short schedule.

02:02

And into this, we receive in the scheduler, which is called short schedule. Which if we just re-index our workspace, there it is. And we're just going to call that short schedule or you could call it schedule. So we're going to go ahead and take this in, replace this out.

02:20

And now what we can do is say every second or every seconds if we wanted to specify that. So now that we've got this in here, we can run this every second and it's going to be a lot more accurate. Now, we didn't look at how we standard run schedules in Laravel, but this is phpr to schedule run. You can see there are no command schedule ready to be run at the moment.

02:42

Now, with the package that we've used, this is a little bit different. We run short schedule run and that's going to go ahead and hang and wait for these to run through. Now, we don't know what's happening at the moment, but obviously at the moment we are going ahead and running this every second. But we don't have anywhere to see what's actually happening here.

03:02

So I'm going to go over to perform endpoint check and I'm just going to dump out the response or log out the response somewhere. So let's go ahead and log some info here and just say response and status. Now, these will be available in the Laravel log. So let's go ahead and clear that out and then pretty much just go ahead and set these to now.

03:24

And what we should see are two statuses logged out as these run. And there you go. You can see they've been logged out. Now, those dates and times have been incremented now or the time specifically has been incremented now. So if we just left this running in a minute's time or in our case, we've got this set up to a five minute interval, this would then run again.

03:46

So I'm going to go ahead and hang around for a little while and in a few moments we should see the next check being performed. OK, so I've just sat and waited for five minutes and sure enough, the next two requests have come in. Probably better to reduce the frequency of the checks rather than wait around. But there we go. So that's now running nicely on a schedule.

04:08

And of course, we don't have to do anything. Any endpoint that is now created will be automatically checked for the next check date. Now that we have our checks running, though, what we really want to do is start to store the information about each of the checks that we perform. And we're going to do that in the next section.

Episode summary

In this episode, we're moving from manually running our performChecks command to having it run automatically on a schedule. We start off by looking at Laravel's built-in scheduler — but it can only run commands every minute at its most frequent, which doesn't cut it for our needs since we want to check every second.

To solve this, we install the Laravel Short Schedule package, which lets us schedule commands every single second (or even a custom range of seconds). We walk through installing the package, setting up the new shortSchedule method in the console kernel, and updating our checks command to run every second.

After that, we check our logs to confirm everything is working as expected. Now, the endpoint checks run automatically at the right frequency, and we can see their status updates logged in real-time.

Next up, we'll start storing the results of these checks, but for now, we've automated the scheduling process so we don't have to worry about manually kicking things off anymore!

Episode discussion

No comments, yet. Be the first!