Common Media Client Data (CMCD)
source link: https://blog.gslin.org/archives/2024/05/01/11777/common-media-client-data-cmcd/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Common Media Client Data (CMCD)
從 Amazon CloudFront 的公告看到的東西：「Amazon CloudFront now supports Common Media Client Data (CMCD) fields in real-time logs」。
CMCD (Common Media Client Data) 是一個私有的 log format，可以讓 client 透過 HTTP(S) header 回報狀態，所以 AWS 這邊有提到你可以設定讓 CloudFront 記錄下來，然後透過其他軟體分析：
Previously, CloudFront logged CMCD parameters as part of the full query string log field, or the HTTP headers log field. Now, you can simply select to include specific CMCD parameters in your real-time logs and save on compute needed to search and extract the CMCD key-value pairs, and reduce the data set for your log analysis.
現在 CloudFront 則是支援判讀做一些處理：
Starting today, you can enable Common Media Client Data (CMCD) fields in your CloudFront real-time logs. You can select key client-side performance parameters and CloudFront delivery performance parameters in the same log record. This can help you correlate variations in Quality of Experience (QoE) for your viewers to CloudFront performance at the granularity of single viewer sessions, simplifying the troubleshooting of QoE issues that impact your viewers engagement.
看了一下就是定義一些欄位，用 JSON 包起來後讓 client 打回伺服器端，可以利用這些資訊動態從伺服器端調整策略，而不像以前主要的調整策略都放在 client 端。
Related
CloudFront 的 access log 多了一些欄位
CloudFront 的 access log 多了一些欄位可以抓：「Amazon CloudFront now provides seven new data fields in access logs」。 官方這次加了七個欄位，看起來後面六個都還蠻有用的... (第一個 c-port 是 client 的 port，目前只想的到 debug 時可以拿出來看...) 而第二個的 time-to-first-byte 可以拿來分析效能，這是從 CloudFront 的角度來看的。 第三個的 x-edge-detailed-result-type 是錯誤時的處理，讓管理者可以從 access log 直接粗略分析。 剩下的四個都是跟 content type 與 length/range 有關，之前居然沒有嗎...
December 17, 2019In "AWS"
CloudFront 支援 HTTP/3
雖然 HTTP/3 還沒有進到 Standard Track，但看到 CloudFront 宣佈支援 HTTP/3 了：「New – HTTP/3 Support for Amazon CloudFront」。 只要在 CloudFront 的 console 上勾選起來就可以了： 看了看 RFC 9114: HTTP/3 文件裡的描述，client 可以試著建立 UDP 版本的 QUIC 連線，但要有機制在失敗時回去用 TCP 的 HTTP/2 或是 HTTP/1.1： A client MAY attempt access to a resource with an "https" URI by resolving the…
August 16, 2022In "AWS"
Amazon CloudFront 支援 EDNS-Client-Subnet
Amazon CloudFront 今天的新聞：「Improved CloudFront Performance with EDNS-Client-Subnet Support」。 目前 CDN 大多都還是靠 GeoDNS 技術達到分流技術，但另外一方面，Google 的 Public DNS 與 OpenDNS 服務不一定在每個 ISP 都有設機房，這使得 CDN 服務無法靠 DNS server 的 IP address 正確導到離使用者 ISP 最近的 CDN (也就是原文指的 sub-optimal performance)。 EDNS-Client-Subnet 是一個 draft，讓 DNS resolver 可以把 client 的網段資訊帶給 CDN 的 DNS server，進而改善定位。 剛剛測試發現 Akamai 也支援了，在「OpenDNS:…
April 3, 2014In "CDN"
Leave a Reply
Your email address will not be published. Required fields are marked *
Comment *
Name *
Email *
Website
Notify me of follow-up comments by email.
Notify me of new posts by email.
To respond on your own website, enter the URL of your response which should contain a link to this post's permalink URL. Your response will then appear (possibly after moderation) on this page. Want to update or remove your response? Update or delete your post and re-enter your post's URL again. (Learn More)
Post navigation
Recommend
About Joyk
Aggregate valuable and interesting links.
Joyk means Joy of geeK