Every time I peek into the webserver logfiles, I find quite a few 404 requests trying to figure out if certain exploits exist on this server. Now I get that these are automated attempts, and the number of requests coming from one IP show that they try several different exploits and path names. Nevertheless I thought that I don’t need this in my log, and on my webserver. fail2ban for the rescue.
Let’s say I have a Django app users. The admin menu shows this as category Users. That’s ok, but if the website users speak another language I want this name translated. Also I’m not necessarily using Users as name in the admin menu as section name, but can use something more descriptive. Website Users, as example.
The Django administration site comes with a couple of default entries, depending on which apps and middleware is installed.
The Huginn software is not only good for monitoring Twitter feeds, it can also be used to monitor websites for changes.
The Django Web Framework makes it quite easy to add new referenced objects in the admin menu.
After setting up Huginn, and implementing the actions on my todo list, I had a look at the available agents and started thinking what else they can be useful for.
One of the ideas I came up with is monitoring if a website is available, or has some trouble. I already have a monitoring system in place, but it’s a nice exercise to learn more about the other agents.