for consistency, log messages on the alert screen should be sorted with the newest on top
Merge remote-tracking branch 'upstream/master'
Merge pull request #49 from tigertext/master

Moved alerts to mensia; dynamically link to git
Merge pull request #50 from tigertext/master

Filter alerts by severity
Merge remote-tracking branch 'upstream/master'
locking in a version of lager
Logging the hostname of bad packets
Filters for node and role on streaming log page
Merge pull request #51 from tigertext/master

Filters for node and role on streaming log page
merged
merged
Merge branch 'master' of github.com:lookio/popcorn
Using relative, self-updating timestamps
Alert log entries now show newest to oldest
Merge remote-tracking branch 'upstream/master'
optimizing history optimizer...  iterates through the table in the right direction, a single iteration, only checking for severities we have in the database, and reschedules the timer only after successfully iterating
showing the username in the header instead of 'admin'
starting work on a nodes screen.  not functional yet
optimization, this will stop checking mnesia for known nodes on every packet we receive.  it's not the ultimate solution, but it's definitely a huge improvement...  next is to remove the ets lookup to get the pid of the node fsm
Merge pull request #52 from tigertext/master

Relative timestamps; sorting on alerts now newest first