Repository navigation
feat: add the cloud spend anomaly ticket template - #16
Open
RamanKharchee wants to merge 1 commit into
Open
RamanKharchee wants to merge 1 commit into
RamanKharchee wants to merge 1 commit into
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.createand 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.updatedandevent.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 onevent.createdonly, withfailure_policy: continueso a failed investigation still files the ticket.open_ticketdepends on it and is skipped with it on later phases;update_ticketruns onevent.updated/event.resolved.model.ValidateWorkflowand 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.🤖 Generated with Claude Code