Skip to content

feat: implement full per-call analytics layer #227

Closed
#1127
Closed
feat: implement full per-call analytics layer#227
#1127
Labels
prio:lowNice to have, can deferscope:large3+ days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent Systemspec:budgetDESIGN_SPEC Section 10 - Cost & Budget Managementspec:providersDESIGN_SPEC Section 9 - Model Provider Layerspec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow Enginetype:featureNew feature implementationv0.8Minor version v0.8v0.8.4Patch release v0.8.4
@Aureliolo

Description

@Aureliolo
Aureliolo
opened on Mar 10, 2026

Summary

The spec describes expanded per-call metadata for comprehensive financial and operational reporting. Not implemented beyond proxy metrics.

Design Spec Reference

  • §10.5 M5+: Full Analytics Layer

Scope

  • Per-call tracking: latency_ms, cache_hit, retry_count, retry_reason, finish_reason, success
  • Aggregation dimensions: per_agent_daily, per_task, per_department, per_provider, orchestration_ratio
  • Tiered alerting for orchestration ratio and retry rates
  • Integration with existing CostRecord and structured logging

Metadata

Metadata

Assignees

No one assigned

    Labels

    prio:lowNice to have, can deferscope:large3+ days of workspec:agent-systemDESIGN_SPEC Section 3 - Agent Systemspec:budgetDESIGN_SPEC Section 10 - Cost & Budget Managementspec:providersDESIGN_SPEC Section 9 - Model Provider Layerspec:task-workflowDESIGN_SPEC Section 6 - Task & Workflow Enginetype:featureNew feature implementationv0.8Minor version v0.8v0.8.4Patch release v0.8.4

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions