Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
bbrazil
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
91.
▲
by
bbrazil
10y ago
Are there performance numbers available? We're on the look out for suitable remote storage for prometheus.io, and would want to know the hardware that'd be required to handle 1M samples/s and how many bytes a sample takes up.
92.
▲
by
bbrazil
10y ago
We plan on seamlessly integrating with long-term storage ( https://prometheus.io/docs/introduction/roadmap/#long-term-s... ) and OpenTSDB is one option for that for us. Ignoring that as it's planned work,
93.
▲
by
bbrazil
10y ago
Speaking as a Prometheus developer, each is suited to different things. For example if you want to store timeseries data long term and already use HBase then OpenTSDB is a good choice. On the other hand if you want to do monitoring that
94.
▲
Optimising a US business trip
(robustperception.io)
1 points
by
bbrazil
10y ago
|
0 comments
95.
▲
by
bbrazil
10y ago
> There is a limit to a node, 800k metrics per box is not that huge when you consider the things that could be measure just on a single host. We have several thousand metrics coming out of just a single MySQL instance. To clarify, that&#
96.
▲
by
bbrazil
10y ago
> I can understand the reasoning behind them building for a single node. Building distributed systems is hard, not everyone is capable of building these systems. They also require languages and frameworks suited to working in clusters. G
97.
▲
by
bbrazil
10y ago
No, the flags libraries I've used had exactly that issue. When that came up what you'd do then is refactor that to be a class parameter or config option or whatever (and we'd usually ask that the flag be kept in some form). U
98.
▲
by
bbrazil
10y ago
> Most places have no outbound port restrictions, or when they do they usually always have a proxy for traffic to go out (like https for updates etc) Depends which company. For companies that really care about security, letting arbitrary
99.
▲
by
bbrazil
10y ago
This defeats the purpose of a good flags library though. Where flags shine is when you've some obscure tunable deep in the dependency tree that you need to tweak (particularly in an emergency). Plumbing through potentially thousands of
100.
▲
by
bbrazil
10y ago
Speaking for Prometheus, it scales down quite well. If anything it's probably easier to run at the smaller scales. That's not true for many other Google technologies. We do assume that you have your house in order configuration ma
101.
▲
by
bbrazil
10y ago
You'd lose annotations and other metadata doing that, plus it's another hop on the critical path of alerting. Probably not the wisest of ideas. You want your alerts coming from as close to what you're monitoring as possible.
102.
▲
by
bbrazil
10y ago
> Not only that, only scaling vertically on a single node doesn't seem like a good design. For Prometheus at least, we're so efficient that it actually works out okay for the vast majority of users. You'd typically need th
103.
▲
by
bbrazil
10y ago
It's advised not to use the pushgateway in that fashion, it's for service-level batch jobs - not trying to subvert your organization's network security policies. See https://prometheus.io/docs/practices&#
104.
▲
by
bbrazil
10y ago
Prometheus developer here. To make it highly available, just run two identical Prometheus servers. That way if either fails the other is still sending alerts, and if both are working the Alertmanager will automatically deduplicate the alert
105.
▲
by
bbrazil
10y ago
HTTPS requires additional round trips, so slows things down and tends to reduce revenue by a non-trivial amount.
106.
▲
by
bbrazil
11y ago
ML is machine learning. Magic Systems is anything other than a manually configured (mostly) simple threshold for alerting.
107.
▲
by
bbrazil
11y ago
> When it is handed over the SREs get all the keys to the kingdom and have the rights, responsibility and ability to fix bugs in the software they're running. Bug fixing is still the responsibility of the developers, which isn'
108.
▲
by
bbrazil
11y ago
> Avoiding magic includes avoiding ML? When it comes to alerting, yes. I've seen it tried many times by competent engineers. The problem is that once you get beyond toy examples into situations with even a mere 10k time series there
109.
▲
How does a Prometheus Counter work?
(robustperception.io)
1 points
by
bbrazil
11y ago
|
0 comments
110.
▲
by
bbrazil
11y ago
Sidekiq is a good example, the author talks about it at https://changelog.com/92/
111.
▲
by
bbrazil
11y ago
There's nothing to stop somebody else from coming along and building a version with clustering support. Whether that will happen or not is, of course, an open question. Clustering is really really hard. My personal experience with th
112.
▲
by
bbrazil
11y ago
http://flabbergast.org/ is the closest, and in a similar vein you'd have https://github.com/google/jsonnet and then Nix. Configuration management is a very different thing to what most of ansible&
113.
▲
by
bbrazil
11y ago
One of my clients got Graylog up and running pretty quickly. Logs are only one part of monitoring though, and it's easy to miss the wood for the trees if you're drinking from the logs firehose. Some metrics monitoring is also vita
114.
▲
by
bbrazil
11y ago
As an example, "ancient" for many projects means two years. That's when enterprises might start considering moving onto that version, so the incentives aren't really aligned here.
115.
▲
by
bbrazil
11y ago
https://en.wikipedia.org/wiki/Michelson_interferometer Basically fire two lasers at right angles to each other at mirrors, and see the pattern when they bounce back.
116.
▲
by
bbrazil
11y ago
The going rate for setting up an Irish company is around €250, and mine only took a few days. Getting an Irish bank account is painful though, and that's with me being Irish in Ireland. I wouldn't try it from Portugal - though pre
117.
▲
by
bbrazil
11y ago
Logs and metrics service different needs, I wrote recently on this: https://blog.raintank.io/logs-and-metrics-and-graphs-oh-my/
118.
▲
by
bbrazil
11y ago
> (reads local stats from files or proc or whatever) If there's useful stats from /proc we're missing, we accept PRs. > about half run on the Prometheus node itself and talk to services like ElasticSearch or Postgres. T
119.
▲
by
bbrazil
11y ago
> The lack of a plugin system We have many ways to plugin to Prometheus across the ecosystem, the textfile collector you're using is one of them. > You can't run 23 different daemons, each on their own port, to collect stats
120.
▲
by
bbrazil
11y ago
You can only alert in that case if the data starts, and there's no transient issues preventing your monitoring working around the time it stops. Alerting based on state changes is fragile, it's better to compare against what you e
More ›