Smarter Optimization Recommendations and Build Traceability
addedHyphen now delivers more accurate optimization guidance by incorporating additional deployment context before recommending infrastructure changes.
Agent's Optimizer skill now considers current deployment settings, recent deployment activity, and recent optimizer outcomes so recommendations better reflect how an environment is actually configured and what the system has already attempted.
This release also improves build traceability by attaching commit and tag metadata to build records and generating links back to your source control provider when available. Now you can trace commits and tags from deployed instances in your project environment resource diagrams.
What’s new
- Optimizer recommendations now:
- Account for current deployment settings
- Consider the most recent successful deployment run
- Incorporate recent optimizer run history
- Added support for collecting deployment logs from New Relic if configured, alongside cloud provider log sources when performing analysis
- Recommendation generation now uses versioned analysis prompts for improved consistency and auditability
- View deployed app's build metadata by clicking on an instance node in a project environment's resource diagram
- Build records now include:
- Commit SHA metadata when available
- Tag metadata when available
- Source links to commits and tags in GitHub, GitLab, Bitbucket, and Azure DevOps when available
How it works
The Optimizer continues to evaluate workload behavior such as CPU, memory, and traffic signals, but now includes additional deployment context before generating recommendations.
That context includes:
- Current deployment settings
- Recent deployment activity
- Recent optimizer actions for the environment
This helps prevent recommendations that conflict with intended configuration or repeat recent changes (flapping).
Build records now store richer source control metadata so you can trace deployments back to the exact revision or release tag that produced them, with direct links to commits and tags in GitHub, GitLab, Bitbucket, and Azure DevOps when available.
Why this matters
Optimization recommendations are more useful when they reflect how an environment is configured and what has already changed.
- Reduce unnecessary or repeated recommendations
- Align optimization decisions more closely with deployment intent
- Improve confidence in automated and approval-based optimization flows
- Make builds easier to trace back to source control history
Things to know
- These improvements enhance the existing project environment optimization workflow
- Recent optimizer history is now part of recommendation context, but will not be retroactively generated for previous deployment runs
- Analysis prompt versions are tracked for consistency and auditability
- Commit and tag metadata appear on builds when source information is available
- Links are generated automatically for GitHub, GitLab, Bitbucket, and Azure DevOps repositories when detected