Twitter | Pretraživanje | |
✕✕✕✕✕
The official Twitter account of Dwayne 'The Rock' Johnson
10.385
Tweetovi
250
Pratim
8.485
Osobe koje vas prate
Tweetovi
✕✕✕✕✕ 9 h
Odgovor korisniku/ci @bradfitz @dgryski @lostluck
i heard nim is good
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 10 h
Odgovor korisniku/ci @lostluck @dgryski
Interesting is not the word I would choose
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 3. velj
Odgovor korisniku/ci @fatih
RED can indeed be implemented with a single Histogram as long as one of the labels can be used to identify errors. HTTP status code is fine for this, for example.
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 3. velj
Odgovor korisniku/ci @fatih
one Histogram per service for request duration, label for method (gRPC method, HTTP route, etc.), label for result (gRPC or HTTP status code), 10–20 buckets — should be no problem
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ proslijedio/la je tweet
Sid Anand 3. velj
If you plan to be in London this March, be sure to check out my "Modern CS in the Real World" track at QCon London with , , , , , & Liza Fireman
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 2. velj
Odgovor korisniku/ci @dullboy @oldmanuk @krisnova
good quick fix until you need config files
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 2. velj
Odgovor korisniku/ci @bwplotka
depends on execution environment, probably by the time you're passing more than 5 or so flags to start the program successfully you should define a config file or startup script, luckily package ff has you covered there :)
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 2. velj
Odgovor korisniku/ci @krisnova
Env vars aren't discoverable, the only way to learn which env vars a program uses is to grep it's source. They should only be used to populate a flag value if it isn't set explicitly, never as the only way to configure a program.
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @tvii @fatih
Yes
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @tvii @fatih
The "problem" with summaries is that they can't be combined — if you run basically any Prometheus that does math against more than one of them, the results are statistically invalid/meaningless
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @fatih
Short answer: yes Long answer: you should size the buckets with this in mind, i.e. set the highest bucket to whatever value represents "violating all conceivable SLAs" — I put that at ~5s for my web services, above that value granularity is irrelevant, my service is broken
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @kkakkoyun @fatih
of course it depends on what the service is doing 👍
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @kkakkoyun @fatih
Your buckets are a bit wild, do have requests that take 2m to complete? Also you don't need requestsTotal, you get it for free with the duration metric
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @fatih
Buckets determine the granularity/precision of your metrics and so should cover the range of expected values. prometheus.DefBuckets are a good starting point for typical HTTP request handlers
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 1. velj
Odgovor korisniku/ci @fatih
In order to perform meaningful statistics on more than one Prometheus histogram (e.g. taking averages, max over time, etc.) their buckets must be identical. See
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 31. sij
Odgovor korisniku/ci @withoutboats
*raises hand*
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 30. sij
Odgovor korisniku/ci @hdevalence @mycoliza
I'm sorry but I don't agree 🤷
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 30. sij
Odgovor korisniku/ci @mycoliza
i don't really know if this is the best thing to encode in the case bit. maybe not. i do know it's a useful and thoughtful feature, though, and that sniping at it (note: not the same as discussing its merits, as we're doing now) reveals ignorance, not intelligence
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 30. sij
Odgovor korisniku/ci @mycoliza
hence my original tweet: the first enumerated benefit primarily for package producers, the second for consumers
Reply Retweet Označi sa "sviđa mi se"
✕✕✕✕✕ 30. sij
Odgovor korisniku/ci @mycoliza
but that's what it does, right? when you're in package p, capitalized identifiers are part of your advertised API, and you know that at all use sites you're right that due to mandatory(ish) package name prefixing, there isn't as much value in this requirement for consumers
Reply Retweet Označi sa "sviđa mi se"