4 ms·

Hot take: I would love to have service providers show their (down sampled!) Alarms actually used for operational excellence publicly (from a read replica/etc)

Hot take: I would love to have service providers show their (down sampled!) Alarms actually used for operational excellence publicly (from a read replica/etc) Doing so would enforce that you actually have those in place, since they're public and now a marketing point. That said, I get the concern of trolls and competitors trying to get a "low score".

dilyevsky 3y ago
You can show it delayed by like a week maybe
compumike 3y ago
Do you mean something like this page: https://heiioncall.com/status https://heiioncall.com/status ? We use all of these internally at Heii On-Call https://heiioncall.com/ https://heiioncall.com/ , and get paged when any of these triggers are alerting. Edit: the subtle difference from the article is that it sounds like you want historical data, rather than present-state data.
gfv 3y ago
The shining example is https://grafana.wikimedia.org https://grafana.wikimedia.org .
- 2023throwawayy 3y ago
  Interesting their fastest backend response seems to be around 500ms up to a full second.
  - CuriousCosmic 3y ago
    That seems pretty reasonable. That's for the app-server cluster to generate uncached results, and propogate them. In general the app server will do this upon the change occurring, before a user actually asks for the page/information. Users should only really see this when performing "mutable" operations (submitting edits, adding new pages or content) or when searching uncommon queries. I doubt it's anywhere close to the critical path for the average guest, casual user, or even contributor. I'd suspect the only type of user who would find themselves hitting those appserver requests frequently would be moderators and admins.
    - themoonisachees 3y ago
      Also: 500 ms on wikimedia sites is very much still in the "okay" range, subjectively. They aren't really sites that you make requests to every minute, if loading the next article took 500ms every time then so be it.
- hinkley 3y ago
  Any time my coworkers start acting like we are amazing for how many requests we handle per second I send them to wikimedia.org. That'll smack the smug right outta most people.
hinkley 3y ago
Few things burn my butt more than chatting with five people (possibly not even working for the same company) who all see a service down while their status page shows green. The fuck it is. 100% unavailable for 5% of your customers is very different than dropping 5% of requests in a uniform distribution.

dilyevsky 3y ago

You can show it delayed by like a week maybe

compumike 3y ago

Do you mean something like this page: https://heiioncall.com/status https://heiioncall.com/status ? We use all of these internally at Heii On-Call https://heiioncall.com/ https://heiioncall.com/ , and get paged when any of these triggers are alerting. Edit: the subtle difference from the article is that it sounds like you want historical data, rather than present-state data.

gfv 3y ago

The shining example is https://grafana.wikimedia.org https://grafana.wikimedia.org .

2023throwawayy 3y ago
Interesting their fastest backend response seems to be around 500ms up to a full second.
- CuriousCosmic 3y ago
  That seems pretty reasonable. That's for the app-server cluster to generate uncached results, and propogate them. In general the app server will do this upon the change occurring, before a user actually asks for the page/information. Users should only really see this when performing "mutable" operations (submitting edits, adding new pages or content) or when searching uncommon queries. I doubt it's anywhere close to the critical path for the average guest, casual user, or even contributor. I'd suspect the only type of user who would find themselves hitting those appserver requests frequently would be moderators and admins.
  - themoonisachees 3y ago
    Also: 500 ms on wikimedia sites is very much still in the "okay" range, subjectively. They aren't really sites that you make requests to every minute, if loading the next article took 500ms every time then so be it.
hinkley 3y ago
Any time my coworkers start acting like we are amazing for how many requests we handle per second I send them to wikimedia.org. That'll smack the smug right outta most people.

hinkley 3y ago

Few things burn my butt more than chatting with five people (possibly not even working for the same company) who all see a service down while their status page shows green. The fuck it is. 100% unavailable for 5% of your customers is very different than dropping 5% of requests in a uniform distribution.