Skip to content

feat: add the cloud spend anomaly ticket template - #16

Open
RamanKharchee wants to merge 1 commit into
mainfrom
feature/cost-anomaly-ticket
Open

RamanKharchee wants to merge 1 commit into
mainfrom
feature/cost-anomaly-ticket

Conversation

@RamanKharchee

Copy link
Copy Markdown
Contributor

Adds Ticket Cloud Spend Anomalies: each cloud spend anomaly gets one ticket that names its cause and owner, a comment for each day it stays elevated, and a closing comment when spend is back to normal. It only reads and files tickets; nothing in the cloud account is changed.

Decision: Every phase runs the same tickets.create and lets ticket-server turn repeats of the same event into comments, instead of tracking the ticket id between runs; nothing else can look a ticket up by event.

Depends on nudgebee/nudgebee-enterprise#41964 (it sends the daily event.updated and event.resolved). Merge after it. Until it is deployed, only the first ticket is filed.

How to verify: on dev with #41964 deployed, install it on an AWS account with a ticket integration; a spend anomaly produces one ticket with an Owner and a Cause, then one comment per elevated day and one on resolve.

Detail
  • investigate (llm.investigate) runs on event.created only, with failure_policy: continue so a failed investigation still files the ticket. open_ticket depends on it and is skipped with it on later phases; update_ticket runs on event.updated / event.resolved.
  • Checked with runbook-server's model.ValidateWorkflow and by rendering each task through its gonja engine for created, updated, resolved, a missing owner and a failed investigation.
  • python3 scripts/gen_manifest.py && python3 scripts/validate.py → OK: 52 template(s) valid.
  • The assignee is an optional tracker login; the Nudgebee owner is written in the ticket text.

🤖 Generated with Claude Code

One ticket per spend anomaly: the cause found by an investigation and the
owner when it opens, a comment each day it stays elevated, and one when it
resolves.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant