Day-2 operations framework: TTL reaper, monitoring skill, and runbook generation
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- azure, javascript
- Domain
- cloud, devops, observability-sre
Research direction
The issue names metadata.json, git-ape-ttl-reaper.yml (or a gh-aw workflow), /azure-monitor-checker, and @git-ape status . Start by tracing the existing deployment and post-deployment health-check flow and how deployment artifacts are produced. Done means expired deployments are reaped, Azure Monitor alerts and health status work, and runbooks are generated after deployment.
Written by the indexing model from the issue text.
Description
Description
The manifesto describes AI in operations: "incident detection, root cause analysis, and remediation suggestions." Git-ape currently stops at post-deployment health checks. This issue establishes Day-2 operational foundations.
Related: #18 (drift detection — another Day-2 capability)
Scope
- TTL Reaper workflow —
git-ape-ttl-reaper.yml(or gh-aw agentic workflow) that checks deployment TTL (set inmetadata.json) and auto-destroys expired resources after notification. - Monitoring setup — During deployment, auto-configure Azure Monitor alerts for key metrics (availability, errors, latency).
- Post-deploy monitoring skill —
/azure-monitor-checkerthat queries Azure Monitor for resource health status. Enables@git-ape status <deployment-id>. - Runbook generation — Auto-generate operational runbooks from deployment architecture (what to check, how to restart, escalation paths).
- Azure SRE Agent compatibility — Ensure deployment artifacts (architecture diagrams, runbooks) are consumable by Azure SRE Agent.
Acceptance Criteria
- TTL reaper workflow auto-destroys expired deployments.
- Deployments include Azure Monitor alert configurations.
-
@git-ape status <deployment-id>shows resource health. - Operational runbooks generated after deployment.
- Dominant language
- JavaScript
- Stars
- 269
- Forks
- 45
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 15
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/git-ape
-
daily-status report
Difficulty 5/5 Over a week Newbie friendliness 20/100
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
agentic-workflows
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
agentic-workflows
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
agentic-workflows
Difficulty 3/5 1-2 days Newbie friendliness 48/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/skills#96 ·
-
[Block] Latest Posts [Type] Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
sugarlabs/musicblocks#8847 ·