Post: Monitoring with GitHub actions

[ds0nt]

No description provided.

[anhpngt]

Suggested change

	For example, we used this to check if any of our domain certificates were close to their expiry. Each day, a github action runs at 10:45, checks if our certificates are dangerously close to expiring, and posts to our `#monitoring` Slack if any of them are.
	For example, we use this to check if any of our domain certificates are close to their expiry. Each day, a github action runs at 10:45, checks if our certificates are dangerously close to expiring, and posts to our `#monitoring` Slack if any of them are.

probably should use present tense I think

[anhpngt]

Suggested change

	schedule: # run at 010:45 UTC daily
	schedule: # run at 10:45 UTC daily

[anhpngt]

Suggested change

	To do this, were going to use three Github actions.
	To do this, we are going to use a Github action with 3 sequential jobs.

[anhpngt]

The previous section was talking about certificate expiry, but this section is checking weather instead. This flow is a bit awkward and confusing to me.

Maybe we can add this paragraph:

For simplification and to focus on Github Action, the following example checks and 
reports bad weather instead of our server's certificate. In practice, we can use the 
example to check anything necessary.

[anhpngt]

Suggested change

	# post results
	# post results
	# note that this step only runs when the previous step fails

[anhpngt]

Suggested change

	Then it will run on it's CRON schedule, and you can also dispatch it manually from the actions page to run the check immediately.
	Then it will run on its CRON schedule, and you can also trigger it manually from the actions page to run the check immediately.

[anhpngt]

I finished with my comments. Not much really 😂