On May 19, 2014, at 7:22 AM, Wichert Akkerman <[email protected]> wrote:
> On 19 May 2014, at 13:20, Donald Stufft <[email protected]> wrote: > >> Can you perhaps reproduce this and check the headers? Look for a X-Served-By >> header. I want to make sure that we don't have a cache with a bad config >> loaded. > > I can’t reproduce it - it was a single failing request as far as I could see. > I’ll look for that header the next time I run into this. > >> I'm not entirely great at sorting out graphite, but it appears to be like we >> don't have any elevated error rates except for one spike at ~9:15. I'm not >> sure >> what timezone that is in, probably UTC? > > carbon just stores unix timestamps. graphite-web can be configured with a > timezone; it defaults to America/Chicago, which is apparently a default it > gets from Django. > > Wichert. Here’s the data from Fastly’s Stats Panel: http://cl.ly/image/1N3a3s3Y3J0I Yellow == 2xx responses, Red = 5xx responses. That’s the last 8 hours and appears to be in Eastern (my timezone). ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Distutils-SIG maillist - [email protected] https://mail.python.org/mailman/listinfo/distutils-sig
