bbrazil

12 ms·

61.
by bbrazil 10y ago
Great to see an analysis of the various options. A few corrections on Prometheus: > an AlertManager which handles generating and transmitting alerts Alerts are generated in Prometheus, the Alertmanager then groups, deduplicates and trans
62.
by bbrazil 10y ago
I bought a infrared thermometer as a gadget, and have found it to be invaluable for cooking.
63.
by bbrazil 10y ago
I like the idea of innovation tokens: http://mcfunley.com/choose-boring-technology Basically you get 3 things per project where you can use something that's not tried and true.
64.
by bbrazil 10y ago
In Ireland that's called a "principal private residence" or PPR. There are cases where it'd make sense to live elsewhere though not legitimately, for example the rent-a-room scheme (can rent a room for up to 1k/mont
65.
by bbrazil 10y ago
A time series database is anything that stores data with time attached, so log storage does count. The more pertinent difference is event logging vs. metrics. For the former the ELK stack is popular, and Prometheus.io is suitable for the la
66.
by bbrazil 10y ago
Prometheus can do 800k/s on a single machine. Handling a million per second sounds perfectly plausible to me if you design it properly. The question is more how much it's going to cost you. Wavefront doesn't publish pricing,
67.
by bbrazil 10y ago
> The killer feature here is the query language. I don't think there is anything else on the market that has its level of sophistication. I've had ex-Googlers on my team who "grew up" with Borgmon, which is in some se
68.
by bbrazil 10y ago
> they skipped all the hard stuff (single node only, no HA We skipped the hard stuff on purpose, as hard stuff is extremely tricky to get right and liable to fail right when it's most needed. See http://www.robustpercepti
69.
by bbrazil 10y ago
> stream are the superior approach in my point of view as they allow for realtime approaches and stream (window based) analytics. I'd see them as slightly different approaches to providing fundamentally the same solution. One builds
70.
by bbrazil 10y ago
> Passive reports can go to any node; a simple load balancer will work fine without any form of hashing or federation required. How do you re-combine and alert on data for one service that got reported to multiple nodes? This would imply
71.
by bbrazil 10y ago
How does this tell you that something is missing if it never reported, or that something is no longer meant to exist?
72.
by bbrazil 10y ago
> you MUST learn Clojure (which can be hard to get a whole team to agree to) For any sufficiently advanced monitoring system, you're going to have to learn some form of DSL/language to take advantage of it. I wouldn't cons
73.
by bbrazil 10y ago
> but I won't use Prometheus, because of the active polling model. > [Grafana+Ichinga] they're so rock solid (and scale like mad) I have a hard time not recommending them. As a Prometheus developer I have seen a significant
74.
by bbrazil 10y ago
There is no first-class push option. I don't see why processing pipelines would be special for push vs. pull, it's generally a wash.
75.
by bbrazil 10y ago
It's open source, so there's no charge for the software.
76.
by bbrazil 10y ago
For logs you're looking at the ELK stack, for tracing Zipkin.
77.
by bbrazil 10y ago
There's a few, here's a recent talk by Weave for example: http://www.slideshare.net/weaveworks/kubernetes-and-promethe...
78.
by bbrazil 10y ago
http://www.robustperception.io/scaling-and-federating-promet... explains it. Unless you're absolutely massive, it's fairly easy.
79.
by bbrazil 10y ago
I'm not sure there is a typical user. We've got everything from single-sysadmin small companies to Fortune 500s to companies looking to integrate it into their products. https://prometheus.io/blog/2016/03
80.
by bbrazil 10y ago
We've a slightly different computational model, so that takes two passes. You can calculate the highest value now (topk) or the highest averages (topk+avg_over_time) and now that you know which timeseries you want, graph those. I belie
81.
by bbrazil 10y ago
That's exactly our thinking, and why we want to minimise dependencies - including internet access.
82.
by bbrazil 10y ago
There's noone presently offering that, it's designed more with a view to being on-prem for reliability ( http://www.robustperception.io/monitoring-without-consensus/ ).
83.
New Features in Prometheus 1.0.0(robustperception.io)
4 points by bbrazil 10y ago|0 comments
84.
by bbrazil 10y ago
> Ireland does not have complex public health service like the NHS. Ireland has a complex public health system whose cost is comparable to the NHS, it is however not of the same quality.
85.
by bbrazil 10y ago
> (less of a problem today, with systemd everywhere) Systemd is far from everywhere. Ubuntu 14.04 doesn't use it and is supported until 2019. Debian Wheezy is supported until 2018. RHEL 6 has support through to 2021. Overall this me
86.
by bbrazil 10y ago
The https://github.com/prometheus/pushgateway serves those cases, primarily service-level batch jobs.
87.
by bbrazil 10y ago
These would be the exact details I'd need to advise you. It depends on how many jobs you have, how much churn there is, and what exactly you want to monitor. If jobs are short-lived then tracking individual jobs would be unwise, someth
88.
by bbrazil 10y ago
> Umm, yeah, but well, isn't that the punchline of every monitoring project? ;-) No actually :) From reading countless websites for the multitude of monitoring solutions out there, the standard pitch is that they'll make your o
89.
by bbrazil 10y ago
Prometheus developer here. > Did you (or has anyone else) migrate your legacy data from graphite to prometheus? Prometheus isn't intended as a long-term data store, so there's usually not much point. The data model is also quit
90.
by bbrazil 10y ago
Prometheus developer here. > More development resources? Not directly. I expect the gains to be around the legal and organisational stuff you need as a project grows (e.g. trademark registration, formal governance), as well as publicity.

More ›