Skip to content

Phase 3.1: Production Deployment - Metrics Agent #2119

Open

Description

@ashleyshaw

Objective

Deploy metrics-collection workflow to production with automatic scheduling.

Deliverables

  • Enable metrics-collection.yml workflow on main/develop
  • Configure scheduled run: daily at 2 AM UTC
  • Set up GitHub token and environment secrets
  • Enable workflow logging and monitoring
  • Configure failure alerts (Slack notifications)

Acceptance Criteria

  • Workflow runs automatically on schedule
  • Metrics collected successfully within <5 minutes
  • Zero authentication or permission errors
  • Failure notifications working

Estimate: 3-5 hours

Related: Metrics Agent Phase 3 Project, Task 3.1


Definition of Ready (DoR)

  • Clear problem statement and expected outcome
  • Acceptance criteria defined
  • Related issues/dependencies identified
  • Required resources/approvals listed

Owner / Assignee

Responsible Party: [To be assigned]

Definition of Done (DoD)

  • All acceptance criteria met
  • Changes tested and validated
  • Documentation updated
  • Changes merged and deployed
  • Stakeholders notified

Spec 020 programme alignment — Tier 7

Keep this issue scoped to its existing workflow-deployment outcome; it does not establish portable metrics-agent implementation or readiness. Verify current workflow behaviour, permissions, scheduling, collected data and alert delivery before treating checked criteria as evidence. Record metric definitions, source coverage and collection failures. Production scheduling, credentials and notification changes require an exact preview and approval; never include secret values in issues or reports.

Programme Tier 7 describes delivery sequencing, not native priority. Each delivery slice must record its exact branch and base, PR title, live template, verified labels, assignee, changed-file scope, tests and closure criteria before implementation. Reuse matching existing work. Stack PRs only for a demonstrated dependency, with merge and retargeting order documented.

Activity

  1. linear-code commented on Aug 19, 2026

    @linear-code
  2. github-actions commented on Aug 19, 2026

    @github-actions
    Contributor

    ⏱️ Aging and SLA annotation

    • Age: 0 day(s)
    • SLA state: Within SLA
    • Thresholds: warn at 7 days, breach at 14 days
    • Last updated: 2026-08-19T09:15:12.078Z

    Maintained by project-meta-sync workflow.

  3. github-actions commented on Aug 19, 2026

    @github-actions
    Contributor

    ✅ Template check passed after update. Thanks for fixing the issue body.

  4. added a commit that references this issue on Aug 27, 2026
  5. self-assigned this
    on Aug 29, 2026
  6. added this to the v1.1 milestone on Aug 29, 2026
  7. github-actions commented on Sep 9, 2026

    @github-actions
    Contributor

    ⚠️ Bare Labels Detected

    This issue has labels that are not in the canonical taxonomy:

    • migrate:area:ci
    • migrate:priority:important
    • migrate:status:needs-more-info
    • migrate:type:task

    Valid Canonical Labels

    Please use labels with a prefix from the canonical taxonomy:

    • Type: type:bug, type:feature, type:task, type:documentation, etc.
    • Status: status:needs-triage, status:in-progress, status:done, etc.
    • Priority: priority:critical, priority:high, priority:normal, priority:low
    • Area: area:ci, area:docs, area:labels, area:security, etc.
    • Meta: meta:needs-changelog, meta:duplicate, meta:blocked, etc.

    For the complete list, see .github/labels.yml.

  8. eleshar commented on Sep 23, 2026

    @eleshar
    Contributor

    Closing as stale: no linked open PR and no activity since 2026-08-19, and it belongs to a plan that predates the current agents and skills consolidation (#3464). Reopen if it is still needed.

  9. eleshar commented on Sep 23, 2026

    @eleshar
    Contributor

    Reopening: this is planned work that has not started, not work that is superseded. It should not have been closed in the #3464 sweep. Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Fields

Priority

None yet

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions