yutori-api-monitor

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

API & Changelog Monitoring

API与变更日志监控

Set up monitoring for API or service changes.
Create a scout with this query structure:
**Context:** Monitoring API stability and changes for $ARGUMENTS to ensure our integration stays up-to-date.
设置API或服务变更的监控。
使用以下查询结构创建scout:
**上下文:** 监控$ARGUMENTS的API稳定性与变更,以确保我们的集成保持最新状态。

What to Monitor

监控内容

  • Breaking Changes: API version changes, deprecated endpoints, removed features
  • New Features: New endpoints, parameters, capabilities
  • Rate Limits & Quotas: Changes to limits, pricing tier updates
  • Deprecation Notices: Sunset timelines, migration guides
  • Security Updates: Authentication changes, security advisories
Sources to check: Official changelog, documentation, developer blog, GitHub releases, status page, developer Twitter/X account
Exclusions: Minor bug fixes, internal refactoring, documentation typos
  • 破坏性变更: API版本变更、已弃用的端点、移除的功能
  • 新功能: 新端点、参数、功能
  • 速率限制与配额: 限制变更、定价层级更新
  • 弃用通知: 停用时间表、迁移指南
  • 安全更新: 认证方式变更、安全公告
检查来源: 官方变更日志、文档、开发者博客、GitHub发布页、状态页面、开发者Twitter/X账号
排除项: 小bug修复、内部重构、文档拼写错误

Deliverables

交付成果

Frequency: Every 12 hours
Output format:
  1. URGENT section for breaking changes (if any)
  2. Table of changes: Date, Type (breaking/feature/deprecation), Description, Migration Required (yes/no), Source Link
  3. Recommended actions for each change

Use `create_scout` with:
- `query`: The above structured query with $ARGUMENTS replaced
- `output_interval`: 43200 (every 12 hours)

After creation, explain:
- Scout will check twice daily for changes
- Critical for staying ahead of breaking changes
- Can set up webhook for immediate notifications
频率: 每12小时一次
输出格式:
  1. 紧急部分(若存在破坏性变更)
  2. 变更表格:日期、类型(破坏性/功能/弃用)、描述、是否需要迁移、来源链接
  3. 每项变更的建议操作

使用`create_scout`时需指定:
- `query`:将上述结构化查询中的$ARGUMENTS替换为实际内容
- `output_interval`:43200(即每12小时)

创建完成后,说明:
- Scout将每日检查两次变更情况
- 对于提前应对破坏性变更至关重要
- 可设置webhook以获取即时通知