{"id":393,"date":"2011-12-16T15:47:21","date_gmt":"2011-12-16T20:47:21","guid":{"rendered":"http:\/\/irreal.org\/blog\/?p=393"},"modified":"2011-12-16T15:47:21","modified_gmt":"2011-12-16T20:47:21","slug":"filtering-log-files-stored-as-lisp-with-emacs","status":"publish","type":"post","link":"https:\/\/irreal.org\/blog\/?p=393","title":{"rendered":"Filtering Log Files Stored As Lisp With Emacs"},"content":{"rendered":"\n

Yesterday, I wrote about transforming log files stored as Lisp<\/a>. Today, I want to continue that theme by considering how we can have the log file filter itself so that we can pick out records meeting certain criteria. I wasn’t going to bother with this but it’s so easy once you have the infrastructure set up, I thought it might be fun to explore it a bit. Yesterday, I worked in Common Lisp, today, just for variety, I’ll work in Emacs Lisp. <\/p>\n

For the benefit of those just joining the discussion, here is a typical record (from Steve Yegge’s The Emacs Problem<\/a>). <\/p>\n

(record\n  (date \"2005-02-21T18:57:39\"<\/span>)\n  (millis 1109041059800)\n  (sequence 1)\n  (logger nil)\n  (level 'SEVERE)\n  (class \"java.util.logging.LogManager$RootLogger\"<\/span>)\n  (method 'log)\n  (thread 10)\n  (message \"A very very bad thing has happened!\"<\/span>)\n  (exception\n    (message \"java.lang.Exception\"<\/span>)\n    (frame\n      (class \"logtest\"<\/span>)\n      (method 'main)\n      (line 30))))\n<\/pre>\n
 To help me in developing code for this post, I duplicated this record 4 times, changing some of the fields, wrapped it in a (log ...)<\/code> sexpr, and put it in the variable log-file<\/code>. As we did yesterday, we start by making each of the tags executable. To start, we define record<\/code>, exception<\/code>, and frame<\/code> as functions that perform an and<\/code> operation on their arguments. The record<\/code> function is defined as <\/p>\n
(defun<\/span> record<\/span> (&rest<\/span> args) (every 'identity args))\n<\/pre>\n
(defun<\/span> date<\/span> (&rest<\/span> args) t)\n<\/pre>\n
 Now let’s suppose we only want to see records that have a level<\/code> of SEVERE<\/code>. We redefine level<\/code> as <\/p>\n
(defun<\/span> level<\/span> (s) (eq s 'SEVERE))\n<\/pre>\n
 and filter out the other records by running <\/p>\n
(remove-if-not 'eval (cdr log-file))\n<\/pre>\n
 The remove-if-not<\/code> function filters out any records that fail the \u201cpredicate\u201d eval<\/code>. Because eval<\/code> evaluates the record<\/code> sexpr it returns a t<\/code> or nil<\/code> value for each record. In this case, records without a level of SEVERE<\/code> will have level return nil<\/code> and therefore record<\/code> will also return nil<\/code> and therefore be filtered out. <\/p>\n
 We can build up more complicated conditions if needed. For example, if we want to see only records with a level of SEVERE<\/code> and a line<\/code> greater than 30, in addition to redefining level<\/code>, we would also redefine line<\/code> as <\/p>\n
(defun<\/span> line<\/span> (l) (> l 30))\n<\/pre>\n
 and run the remove-if-not<\/code> function on log-file<\/code>. <\/p>\n
 If you’re interested in this sort of thing, here are some problems to think about <\/p>\n
    \n
  1. How would you filter on\n
    level equals SEVERE or line > 30\n<\/pre>\n<\/li>\n
  2. Notice that method<\/code> appears twice in the record. How would you    filter on the one that’s in the frame<\/code> sexpr? <\/li>\n
  3. How would you handle general queries such as\n
    (level equals SEVERE or line > 30) and thread equals 10\n<\/pre>\n<\/li>\n<\/ol>\n
    I’ll give my answers to those questions in the next installment. <\/p>\n
     It might seem like this is a lot of work to run a query given that there are general tools available for doing so but it doesn’t take nearly as much effort as you might think. First of all, you would have a lot of these functions already defined so that you can just paste them into your buffer, redefine the filtering conditions, and run the filter. In the next installment, I’ll talk about how writing these functions, even if you don’t already have them, is really easy when you leverage the power of Emacs. I’ll also discuss how I used Emacs to develop and test the code interactively as I went along. <\/p>\n","protected":false},"excerpt":{"rendered":"
    Yesterday, I wrote about transforming log files stored as Lisp. Today, I want to continue that theme by considering how we can have the log file filter itself so that we can pick out records meeting certain criteria. I wasn’t … Continue reading →<\/span><\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[9],"tags":[18,28,14],"class_list":["post-393","post","type-post","status-publish","format-standard","hentry","category-programming","tag-emacs","tag-emacs-lisp","tag-lisp"],"_links":{"self":[{"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/393","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=393"}],"version-history":[{"count":0,"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=\/wp\/v2\/posts\/393\/revisions"}],"wp:attachment":[{"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=393"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=393"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/irreal.org\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=393"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
 and the other two are the same except for their names. See Applying and And or In Emacs<\/a> for why something like (apply 'and args)<\/code> won’t work. The other tags are defined as functions that just return t<\/code>. For example, date<\/code> is <\/p>\n