jamtur01

I am sorry but you're delusional if you think any of that is happening and they're acting in a legal manner. A small sample of the links in that post show ICE are actively violating constitutional rights and flaunting the rule of law. This same organization is actively ignoring a federal judge's orders to not use crowd control weapons on people who pose no threat.

You are familiar with the 4th Amendment? These acts are a clear violation of 4th Amendment rights, rights which extend to both citizens and non-citizens.

Very open - Python is one of the better communities out there for openness and inclusion. The pip folks are lovely people and would welcome your help - https://pip.pypa.io/en/latest/development/.

You can alert via a number of mechanisms: email, PagerDuty, Slack et al, etc (I talk about most of those in Chapter 9).

I have never been very keen on alerting dashboards, I find they are rarely actually reviewed and flash red for days or weeks. :) So I only covered metrics/graphing as a console rather than a status console. If you want to add such a console it'd be easy to output Riemann events via an API to such a console.

Glad you enjoyed the book!

Sorry - must have fumbled Update button. Now there.

Definitely interested - email is in profile.

Thanks - good idea - will do that.

It provides several example applications and goes through the tools.

Thanks - I added a pricing panel.

Thanks mate - very kind!

It's a spectrum to me. We're way behind the curve on monitoring and the "state of the art" in, anywhere but cutting edge shops, is woeful. I'd love folks to be able to anomaly detection easily and simply but the technology and tools aren't quite there yet. I am just hoping to get folks to advance their environments a little way forward.

Thanks - I considered that but I don't like to put barriers in people's way - especially for free content. I don't like to be too marketing-esque. Just not in my nature. :) A couple of thousand folks signed up to the mailing list using the current approach, which I'm pretty happy with.

Thanks for your feedback.

1. I decided not to do this because my experience is that people like to do something practical first. I've had a huge response to that chapter - lots of folks have gotten into Riemann that had previously been stuck. That alone is a solid +++ for me.

2. Each chapter contains some discussion of capacity planning for specific tools, where relevant.

3. The capstone chapters (11-13) discusses this, as do the chapters covering logging and application instrumentation.

4. Thanks - I'll consider that.

5. I discuss in various chapters visualization but I've found that most folks have very different needs and desires. So I focussed on discussing what to show in small segments as well as some visual design discussion rather than a specific chapter on dashboarding/reporting. Hard choice but a 750 page book needs to stop somewhere. :)

Thanks for taking the time to comment - it's awesome when folks share their thoughts!

That's mostly correct. I have a chapter on adding instrumentation to applications with examples in Ruby/Rails and Clojure that can easily be adapted to other languages and frameworks. I also cover adding structured logging to your applications.

Not as this stage - my experience with how fast physical books date hasn't been good.

Thanks - I'll consider that.

I usually find a template I like and modify it. I really should start paying someone. It's not my core skillset. :)

Love Riemann. So much that I'm writing a book about monitoring with Riemann as the core routing engine:

http://artofmonitoring.com/

There's a sample chapter available, which covers the initial Riemann implementation and a Clojure "getting started" guide which should help anyone - even if you're not interested in the rest of the book! :)

http://artofmonitoring.com/TheArtOfMonitoring_sample.pdf

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Non-US projects already use Stripe. This moves means both US and non-US projects will use Stripe.

Currently we don't have any plans to make it a separate repository. This is largely because of packaging issues - most of the distros currently struggle with packaging Go components. We're working closely with them to make this better but in the meantime libcontainer lives in the pkg/ directory to make it easier for us to ship Docker.

You can most certainly use netlink in the same way and we'd love a PR for IPv6 support for it!

Yes. That's a change we've got planned and we're working with the Ubuntu/Debian packagers.