lennartkoopmann

I was always afraid of browser extensions and now I'm also afraid of IDE extensions. Recently came across SecureAnnex[0] and it looks promising to get some control over it.

[0] https://secureannex.com/

Oh, I love that!

In another thread, someone else pointed out that I could be wrong about the observation car access. I added a note to the post! :)

Thanks! I added a note to the blog post, saying that I might be wrong here.

> I mean... which one? ;)

I'm from Houston. I'll take any public transport. ;)

I've seen people being turned around. Not sure if that's what usually happens or if I misinterpreted the situation.

Ha, I believe I stepped out there for a few minutes though. :)

Gotta get out of Gmail and Excel from time to time. :D

Whoops! Thank you. :) Fixed.

Here is a video of me listening to the repeater while the ISS passes over Houston, TX at night: https://twitter.com/_lennart/status/1305685955370725376

I wrote a blog post a while ago: https://www.wtf.horse/2017/09/19/common-wifi-attacks-explain...

> Kurz vor 13 Uhr hat die Firma den Zugriff auf die Daten gestoppt.

Translation: "The company [Zyxel] blocked access to the data right before 1pm."

Graylog has this out of the box since v2.0 and integrated with the authentication layer: https://www.graylog.org/blog/55-announcing-graylog-v2-0-ga

It is fairly easy to set up centralized logging. Interdependencies between services can be pretty complex. Think about it from the operations and not the development side: Which firewalls are between the public internet and service X? Why are two Windows workstations talking to each other? Which services are talking to an internal API?

The moment more than a few people are involved with your systems, it can get so complex that visualizing dependencies can be extremely helpful and bring a lot of insights.

... and Graylog CTO here. Ask us anything! :)

They triangulated it using the three microphones I guess. Also I guess you can figure that out by looking at the debris pattern because they seem to have a lot of knowledge about the used rocket.

Take a look at Graylog: www.graylog.org

We decided to drop the "2" from the name to have less confusion with "Graylog(2) 2.0" - Point taken here, the initial "2" was not a good idea :D

(The documentation may need a "History" page)

Ok. I have used Sentry the last time a long time ago and maybe I'm outdated.

I suggest you try out Graylog and let us know about your findings! I'll make sure to look at Sentry again.

This might help: http://docs.graylog.org/en/1.0/pages/ideas_explained.html

Sentry is for monitoring exceptions and errors on your platform. While Graylog can do that, too (without the aggregation though) it is also capable of monitoring any log messages out there and not only errors.

Yes, you can set up as many Graylog servers as you want and put them behind a load balancer or integrate any kind of failover you want.

We do not recommend it running on extremely small platforms like a raspberry pi, but a very small VM (we have OVAs and other virtual appliances ready) is able to process a lot of messages already.

Yes! We have put a lot of effort into making this one thing.

The graylog-web-interface connects to the graylog-server REST APIs and that is it. You can manage and monitor the whole system from the graylog-web-interface.

Both components are always released together.

Yes! Let me know if we can help with any questions.

See also: http://www.infoworld.com/article/2885752/log-analysis/open-s...

Exactly. Think of this search query you could do:

  source:your-app AND http_status_code:>=500

This would give you a list of all HTTP 500s of "your-app".

Or:

  user_id:12346 AND http_status_code:>=500

... to see all errors a user caused after customer care called you, reporting an error the user got. Stacktrace is there immediately without having to find the right log file on the right web server.

A log management tool: You send all your local log messages/files to a central place (Graylog) and have unified searching, filtering, monitoring, alerting, forwarding, ...

All open source.

That is a very good point. We are in the process of changing that. :)

The meaning should be that with v1.0 it is finally very hard to crash the system by overloading it. Previous versions were easier to crash by filling memory in load spike situations for example.

It's all open source, you can feed any data, not only sylog and TORCH (http://www.torch.sh) is selling commercial services.

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!

Please contact the mailing list and we are happy to help. 300 msgs/sec is not much and we should easily get that unter control. :)

That doge reference in the screenshot actually made it there by mistake. :)