<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>drush on Daniel Wehner's blog</title><link>https://daniel.town/categories/drush/</link><description>Recent content in drush on Daniel Wehner's blog</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 08 Jan 2016 00:00:00 +0000</lastBuildDate><atom:link href="https://daniel.town/categories/drush/feed.xml" rel="self" type="application/rss+xml"/><item><title>Make sense of your watchdog entries</title><link>https://daniel.town/make-sense-of-your-watchdog-entries/</link><pubDate>Fri, 08 Jan 2016 00:00:00 +0000</pubDate><guid>https://daniel.town/make-sense-of-your-watchdog-entries/</guid><description>Websites have errors, which are ideally logged. Logging though is one thing, you also need to make some sense out of them.
In an ideal world you would have some logging server like graylog or similar. Sadly this is not avaiable on every site.
Here is an example of just looking at error messages stored in the database, but the general toolsuite could be applied to everything.
Get the data We use drush to fetch the error messages from drupal:</description></item></channel></rss>