4 ms·

Cool, you just reinvented syslog, poorly.

by tedjdziuba 15y ago

ascendant 15y ago
I'm sure you can come up with more constructive suggestions than just that.
- tedjdziuba 15y ago
  There's value in brevity.
  - troutwine 15y ago
    Yes; criticism delivered with no justification is often simply rude. Perhaps you have a point--it's hard to tell: you didn't make one.
    - tedjdziuba 15y ago
      I said that OP had reimplemented something that already existed, but with fewer features and tests. Or did you get something else out of those six words?
      - troutwine 15y ago
        You have _now_ made that statement. Previously, you merely stated that they had done a poor job of reimplementing syslog without explaining why--this is the sole component of good criticism. Implicit meaning is tantamount to no meaning at all.
e1ven 15y ago
Syslog is cool and all, but this is a nice UI for displaying the logs in the browser, so everyone in the company can watch them, or you can easily open it up on an iPad, and hang it on the wall. Could I use SSH over iTerm, and display multiple windows in Screen? Sure. But this is easier/quicker. It would be nice if it didn't need to constantly hit local disk on every machine, though.
- viraptor 15y ago
  What is a usecase for everyone in the company to see raw logs? Nagios / zabbix dashboard - sure. Some visits analytics - maybe. General stats / resource usage - not for everyone, but ok. But why would you ever inflict raw, unprocessed, scrolling logs on anyone other than developers working on a specific bug? (they'd expect an accessible backwards search too)
  - l_adams 15y ago
    I work with Mike. Everyone in the company doesn't need to see the logs, but all the developers do and some others (like myself) do too. This tool is most useful for watching servers after deployments, tracking a process through a bunch of coordinated services, live debugging, or keeping an eye on specific log messages across a bunch of servers. As many folks have pointed out, there are plenty of solutions for aggregating, storing, parsing and analyzing logs. We needed a tool to make watching live logs simpler. That's what this is for.
  - e1ven 15y ago
    I was thinking it would be fun, in a somewhat similar vein to Google displaying Search Queries on the wall - http://www.flickr.com/photos/kchrist/21051526/ http://www.flickr.com/photos/kchrist/21051526/ That said, I agree- Historical Search is a necessary feature for it to be very useful to debugging.
  - prule 15y ago
    I created vsConsole because it was a pain to get access to even the development and test server logs for the apps we were working on. Now the developers and testers have easy access to logs (not just syslogs, but our application logs wherever they may be). http://demo.vamonossoftware.com http://demo.vamonossoftware.com So, I can easily see the use for these kinds of tools. Nagios, Splunk, et al are all too heavyweight for our kind of requirements.
- tedjdziuba 15y ago
  Raw logs generally aren't a useful source of information for humans.

Cool, you just reinvented syslog, poorly.

ascendant 15y ago

I'm sure you can come up with more constructive suggestions than just that.

tedjdziuba 15y ago
There's value in brevity.
- troutwine 15y ago
  Yes; criticism delivered with no justification is often simply rude. Perhaps you have a point--it's hard to tell: you didn't make one.
  - tedjdziuba 15y ago
    I said that OP had reimplemented something that already existed, but with fewer features and tests. Or did you get something else out of those six words?
    - troutwine 15y ago
      You have _now_ made that statement. Previously, you merely stated that they had done a poor job of reimplementing syslog without explaining why--this is the sole component of good criticism. Implicit meaning is tantamount to no meaning at all.

e1ven 15y ago

Syslog is cool and all, but this is a nice UI for displaying the logs in the browser, so everyone in the company can watch them, or you can easily open it up on an iPad, and hang it on the wall. Could I use SSH over iTerm, and display multiple windows in Screen? Sure. But this is easier/quicker. It would be nice if it didn't need to constantly hit local disk on every machine, though.

viraptor 15y ago
What is a usecase for everyone in the company to see raw logs? Nagios / zabbix dashboard - sure. Some visits analytics - maybe. General stats / resource usage - not for everyone, but ok. But why would you ever inflict raw, unprocessed, scrolling logs on anyone other than developers working on a specific bug? (they'd expect an accessible backwards search too)
- l_adams 15y ago
  I work with Mike. Everyone in the company doesn't need to see the logs, but all the developers do and some others (like myself) do too. This tool is most useful for watching servers after deployments, tracking a process through a bunch of coordinated services, live debugging, or keeping an eye on specific log messages across a bunch of servers. As many folks have pointed out, there are plenty of solutions for aggregating, storing, parsing and analyzing logs. We needed a tool to make watching live logs simpler. That's what this is for.
- e1ven 15y ago
  I was thinking it would be fun, in a somewhat similar vein to Google displaying Search Queries on the wall - http://www.flickr.com/photos/kchrist/21051526/ http://www.flickr.com/photos/kchrist/21051526/ That said, I agree- Historical Search is a necessary feature for it to be very useful to debugging.
- prule 15y ago
  I created vsConsole because it was a pain to get access to even the development and test server logs for the apps we were working on. Now the developers and testers have easy access to logs (not just syslogs, but our application logs wherever they may be). http://demo.vamonossoftware.com http://demo.vamonossoftware.com So, I can easily see the use for these kinds of tools. Nagios, Splunk, et al are all too heavyweight for our kind of requirements.
tedjdziuba 15y ago
Raw logs generally aren't a useful source of information for humans.