Count AI agent requests to docs.apify.com at the CDN, as apify.com does

未关闭
  • 哪里不对？
#3,063 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
22/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws
领域
analytics, devops, infrastructure

调研方向

The reference counter is the AIBotTrackingFunction CloudFront function in apify-web's deploy/cloudformation/cdn.yaml, and the docs distribution is defined in deploy/cloudformation/apify-docs.yaml in the private apify-docs-private repo, where DefaultTTL: 86400 sits. Start by reading how the function counts per agent and path, then check whether the docs distribution can attach it. Done means agent requests to docs.apify.com are counted per agent, per path, and per Markdown or HTML request, and appear on the existing agent traffic board.

由索引模型根据 Issue 内容生成。

描述

low priority t-acquisition

Problem

Nothing counts AI agent requests to docs.apify.com. On apify.com, a CloudFront function (AIBotTrackingFunction) counts each agent request by vendor and path, and a board shows which pages agents read, whether they ask for HTML or Markdown, and how often they fetch agent-facing files. The docs CloudFront distribution doesn't run that function, so the same questions have no answer for the ~1,470 .md pages docs publishes, though most of the Apify .md pages Bing's AI answers cite are docs pages.

Done when

  • Requests to docs.apify.com are counted per agent and per path, using the agent buckets apify.com uses.
  • Each count records whether the agent asked for Markdown (a .md URL or Accept: text/markdown) or HTML.
  • The counts appear on a board with the same view as the apify.com agent traffic board.

Constraints

  • The nginx origin logs can't stand in for CDN counting. The docs distribution caches for a day (DefaultTTL: 86400 in apify-docs.yaml), so nginx sees only cache misses.

Source

Hanieh's request in #acquisition-team-collaboration: https://apify.slack.com/archives/C04BTPAF0V8/p1790851249885659?thread_ts=1790151619.210319&cid=C04BTPAF0V8

主要语言
JavaScript
星标
82
派生
240
平均合并
3 天 10 小时
30 天内合并 PR
71

环境准备

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

apify/apify-docs 的其他 Issue

查看 apify/apify-docs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。