#6592 Basic monitoring for Fedora Magazine and Fedora Community Blog
Closed: Fixed 2 years ago Opened 2 years ago by mattdm.

Please check for:

  1. 200 OK HTTP responses from https://fedoramagazine.org/ and https://communityblog.fedoraproject.org/
  2. The strings "Fedora Magazine" and "Fedora Community Blog" in the returned HTML, respectively.

and it'd be nice to have these listed at https://status.fedoraproject.org/

I'm not sure about service level or response, or what kind of outputs. It seems like monitoring is a first step no matter what. :)


status is not a dynamic tool and requires someone in main to push changes to it. I think that adding stuff to it which is not run completely inside of Fedora Infrastructure is not worthwhile at the moment

Oh, I didn't realize that wasn't dynamic. Scratch that part of the request, then.

Metadata Update from @smooge:
- Issue assigned to smooge

2 years ago

I have added basic tests for the text involved. Tests to check if the databases are running will require setup of nrpe on the box and tests for how the dbs are run which will require documentation from the owners.

I think just testing the page contents and that it returns a 200 should be enough...

if the db dies or the like, the page won't have the right contents anymore and should alert.

Metadata Update from @kevin:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata