Graylog2 v0.20.0 released
graylog2.org
graylog2.org
* Graylog2 is probably version 2 of Graylog (fair enough) * It's a data analytics platform, where you can feed your syslog. * Has a REST interface
What I would like to understand but was not able to:
* Do they open source both client and server? * Is it only a server app with a web interface? * To they sell anything at all? (support, plans, etc)
Also take a look at: http://support.torch.sh/help/kb/general/graylog2-architectur...
The feedback here definitely helped us identify that we need to make our websites more obvious about what Graylog2 is actually doing. Thanks!
In an enterprise context with lots and lots of logs Graylog2 is making the process of segregating access to certain logs very,very easy. It's interface is a lot less "bling bling" than Kibana but much easier to use for a certain type of users.
Logstash is still king for parsing logs into structured events (and we use it a LOT - our current config file is ~2.5k lines) but we had issues with stability and loosing messages (crashes due to character issues, etc).
The core of Graylog2 rocks - it's stable and very performant (we are pushing 30k+ msgs/s over a single node with room to spare) and the support we have received from the Graylog2 team has been nothing but awesome.
I am confident that they will catch up with Kibana (in terms of visualisations) very, very quickly.
I eventually had to take it down because it keeps crashing but now I have no error information. Any help would be greatly appreciated.
Also, if you're on the fence about whether to use this or Kibana, they're compatible with each other, so give them both a try. (Set up Graylog2, point Kibana at G2's elasticsearch instance, profit.)
Sorry I don't have anything constructive to post.
It took us a while to build us this foundation but now we are constantly releasing updates on top.
This seems suboptimal from a marketing perspective.
in one of the first screen shots: "wow such monitor"
I'm guessing that was just a test name for the purpose of the screenshot, or so I hope.
However, speaking in general (and not just aiming it at this project), can we please leave the cutesy little Doge talk out of documentation and marketing? I'd say that's true of all "memes" in general. In theory anyone can look at a project if it's useful, and believe it or not, not everyone spends enough time on Reddit or 4Chan to have a clue about what a Doge or a Harlem Shake is.
tldr; such dogetalk. much child-like. so annoy. wow.
And they're going to be harmed by a meme in the URL to the blog post... how?
If I pointed a manager or client at a blog entry that contained grammar that was worse than what my 5 year old nephew utters, it'd reflect on me, or at the very least, the project. Again, I think graylog is a neat project, and their use here really is no big deal, but I think the idea of throwing out intelligent sounding communication in the interest of sounding cute is a very bad idea.
If I had opened an IBM-enterprise-blah wall of text, I'd probably have not spent nearly as much time learning about their product.
"catering to like-minded individuals": yes, people with logs they need to analyze. That could be a 20 year-old with a MBA stickered up, or a 53 year old analyst working inside of a Active Domain enterprise.
(It's still on the screenshots here: http://theold.graylog2.org/about)
Just to clarify, you're on a forum celebrating startups and their culture. For better or worse, that means most folks here are not wearing a tie or heels to work and some even have a sense of humor (I know!). Yet, the only thing you took away from damned near a complete rewrite of a useful product was two tiny meme references that most people wouldn't even notice, then you came to tell this crowd how horrible of a sin that was.
But wait! Down thread you say it's not a big deal. Yet here we are, discussing it.
When people ask me why I'm so dismissive of Hacker News and its regular contributors, I should just start pointing at comments like this. Also, I'll be pitching Graylog2 to executives later this week, and just for you, I'll make my deck's first slide "Much Logging, Such Data."
My use case is (currently) more in exceptions catching than performance monitoring. Judging from that screenshots alone, I would say that Graylog is a better fit for me.
Also Graylog2 has stuff like a user/role model, (authenticated) REST APIs and generally a more integrated approach.
I suggest you give both a spin and decide. :) Both products are easy to setup.
A shame since it should be very easy to implement similar to the REMOTE_USER env in other langs, maybe via X-Authenticated header or something for play.
https://github.com/Graylog2/graylog2-web-interface/issues/56...
You can still expect stuff like the famous Party Gorilla (aka "That drunk sloth") though. ...and rumors are that he might come back in some way.