Project

tailnudge

0.0
No commit activity in last 3 years
No release in over 3 years
Tailnudge displays OS notifications when a tailed file matches a pattern; useful for being nudged more forcibly when you encounter deprecation, errors in log files.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 1.4
>= 0

Runtime

 Project Readme

Tailnudge

Utility to send OSX notifications while tailing one or more files for pattern matches.

Useful if you'd like to be notified when, eg, a log displays a deprecation or error notice during development.

Installation

$ gem install tailnudge

Usage

See:

$ tailnudge help tail

Examples

Tail a log and look for lines that include "DEPRECATION" or "DEPRECATED", and play the "Tink" sound.

$ tailnudge log/development.log -p deprecat -t 'My App' -s Tink

Note that patterns are case-insensitive and that only one notification per pattern will be displayed at a time (to prevent inadvertent event flooding) unless you use the --all/-a option.

Notify Rails HTTP 200 request times, without throttling:

$ tailnudge log/development.log -a -p 'Completed 200 OK in (\d+m?s)' -t 'Requests'

Notify when HTTP 500 or 404 is encountered (but only show one 500/404 notication at a time; no -a option, and throttling is done per-pattern):

$ tailnudge log/development.log -p 'Completed 500' 'Completed 404' -t 'HTTP 404/500'

Notify when HTTP 5XX or 404 is encountered (but only show one 500 or 404 at a time; no -a option, and throttling is done per-pattern):

$ tailnudge log/development.log -p 'Completed [45]\d{2}' -t 'HTTP 4XX/5XX'

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request