Using Server-Time for App and CDN Monitoring

Transcript

2. Using Server-Timing for App and CDN Monitoring Charles Vazac @vazac
3. Olden days of RUM
4. RUM APIs
5. Request
6. Response
10. Response Header Syntax Server-Timing: <name>; duration="<duration>"; description="<description>" Examples: Server-Timing: cache-hit Server-Timing: auth; duration=75 Server-Timing: bytes-on-disk; description=17000 Server-Timing: db; duration=120; description="database access"
11. Browser support
12. Manual Instrumentation Candidates: 1) Database queries 2) Cache lookups 3) API calls 4) Data transformation / processing 5) Image compression 6) Template rendering 7) etc….
27. Privacy & Security
28. CORS
29. TIMING-ALLOW-ORIGIN: www.example.com
30. TIMING-ALLOW-ORIGIN: *
31. CDN
32. #1 Server-Timing: edge; duration=120
33. #2 Server-Timing: origin; description=true -or- Server-Timing: origin; description=false
34. #3 Server-Timing: bytes; description=10799
35. CDN
36. DEMO
37. Collection & Compression
39. resourcetiming-compression.js
42. DEMO
43. Future of Server Timing
45. Links! Server Timing specification https://w3c.github.io/server-timing/ mPulse: https://www.akamai.com/us/en/products/web-performance/mpulse.jsp Libraries: https://github.com/SOASTA/boomerang https://www.npmjs.com/package/resourcetiming-compression https://github.com/Sage/jsurl https://www.npmjs.com/package/express-middleware-server-timing https://github.com/tpeczek/Lib.AspNetCore.ServerTiming https://github.com/dpogue/rails_server_timings
46. Thank You!