bbrazil

16 ms·

121.
by bbrazil 11y ago
The general advice is to run Prometheus behind the firewall, you want as few things between your monitoring and what you're monitoring as possible. This makes it more resilient.
122.
by bbrazil 11y ago
You need a place with all that information anyway, otherwise how do you alert on something being missing? If you can't easily do that with your existing infrastructure, you should fix that first. I've written about this at http:&
123.
Evolving from Machines to Services(blog.raintank.io)
1 points by bbrazil 11y ago|0 comments
124.
Logs and Metrics and Graphs, Oh My(blog.raintank.io)
2 points by bbrazil 11y ago|0 comments
125.
by bbrazil 11y ago
It depends on which services, but for simpler services with well understood open source equivalents (e.g. route53 and BIND) you can probably manage two per sysadmin at a similar quality to AWS with a basic API. For something like RDS or Red
126.
by bbrazil 11y ago
Revoking certificates is a hard problem (how do you know if the CRL is blocked by an attacker, or just down right now?), so instead we rely somewhat on the certs expiring after a while so that they'll eventually get replaced. It also o
127.
It’s overloaded? Try harder(robustperception.io)
2 points by bbrazil 11y ago|0 comments
128.
by bbrazil 11y ago
Prometheus developer here, what do you feel it's missing? Telegraf can both read and produce Prometheus metrics, which is something I've worked on as I believe metrics shouldn't be locked into any one ecosystem.
129.
Do you know what software you’re running?(robustperception.io)
2 points by bbrazil 11y ago|0 comments
130.
by bbrazil 11y ago
Good to know, thanks. We vendor our dependencies so it'll be next release before this will work out of the box.
131.
Do you have basic infrastructure?(robustperception.io)
3 points by bbrazil 11y ago|0 comments
132.
by bbrazil 11y ago
../../Sirupsen/logrus/text_formatter.go:28: undefined: IsTerminal The logrus library we use for logging doesn't support Solaris.
133.
by bbrazil 11y ago
I do nightly binaries for Prometheus in all the possible archs, while things should compile perfectly there can be small things that prevent things from cross-compiling. darwin/arm, darwin/arm64, plan9/386, plan9/amd64 a
134.
by bbrazil 11y ago
As an Irishman, both announces and announce sound fine to me.
135.
by bbrazil 11y ago
Try out Prometheus, you can get it up and running a few minutes. It supports all the functions Graphite does, bar sin() and the Holt Winters functions which we plan on adding.
136.
by bbrazil 11y ago
Kibana is more logging, but Promethues covers the StatsD and Graphite requirements out of the box. Graphfana is one visualisation option to go with that ( http://www.robustperception.io/setting-up-grafana-for-promet... ).
137.
by bbrazil 11y ago
The problem with subresource integrity is that it ties you to one version of the code. That's fine for something like jQuery, but doesn't work in this case where you expect the code to change relatively frequently.
138.
by bbrazil 11y ago
As part of my degree 10 years ago we did wire wrapping to make a simple 68332 computer with serial terminals for I/O. The team I was on was weeks ahead of the others, until we were stuck by what turned out to be one wrong wire. I think
139.
by bbrazil 11y ago
The definition I like is that it's when the size of the data becomes a significant challenge to solving your problem. For example 1TB of data won't fit in memory, but if all you need to do is a sequential read in under a day then
140.
by bbrazil 11y ago
This is basically the approach we take with Prometheus, with the option to add in additional stats like duration and processed records too. http://www.robustperception.io/monitoring-batch-jobs-in-pyth... is the full Python
141.
by bbrazil 11y ago
Syntax and semantics are separate, not having to learn a new syntax is handy. Syntactically the problem I run into is that it's got it's own DSL in task definitions, so it can be hard to keep in mind what's YAML and what&#x27
142.
by bbrazil 11y ago
It should read "split up your monolith". Just because one extreme isn't working for you doesn't automatically mean the other extreme is the right solution.
143.
by bbrazil 11y ago
In Prometheus we solved this by having Histograms where we exported cumulative buckets of latencies, which can be aggregated and then the quantiles calculated from them. http://prometheus.io/docs/practices/histogra
144.
by bbrazil 11y ago
> Health insurance will inevitably start to care about what you eat and how much you exercise. This is already happening, I met the founder of http://wesavvy.com/ recently which uses your phone to track exercise and redu
145.
by bbrazil 11y ago
At least in terms of configuration management, what you usually end up with have is a complex config generated by something that is Turing complete. Better to start out and keep the core configuration representation simple (e.g. json, proto
146.
by bbrazil 11y ago
My personal contribution is http://demo.robustperception.io:9090/consoles/life.html Who doesn't want a Turing Complete monitoring language?
147.
by bbrazil 11y ago
> Once your engineering org gets to be a certain size the benefits you can obtain by investing in making all your engineers slightly more productive start to swamp the slight gains that one team might get from doing things their own, sli
148.
by bbrazil 11y ago
An additional practical difference is that due to tracking less, that metrics can take much fewer resources allowing you to gain insight that's not practical from logs. I'd expect in a well instrumented system that a single reques
149.
by bbrazil 11y ago
It's not just that, EU startups who currently depend on US-based services are going to be in quite a bit of trouble unless they got consent from their users to put their data in the US.
150.
by bbrazil 11y ago
> I wonder if they use exponential backoff? More importantly, did they use randomised exponential backoff? Having all the retires hitting at the same time can lead to a pulses of outages until things settle down.

More ›