cd /news/ai-tools/investigate-what-changed-after-a-dep… · home topics ai-tools article
[ARTICLE · art-29929] src=signoz.io ↗ pub= topic=ai-tools verified=true sentiment=↑ positive

Investigate What Changed After a Deploy with Noz

SigNoz released a new AI-powered tool called Noz that helps developers investigate post-deployment issues by comparing metrics before and after a release. The tool analyzes error rates, latency, and traces to identify what changed and pinpoint the root cause of regressions. Noz provides step-by-step guidance and suggested actions to help teams quickly diagnose and resolve deployment-related problems.

read2 min views5 publishedJun 14, 2026

A deploy went out and your error rate climbed right after. Before you start bisecting commits, you ask Noz what changed between the window before the release and the window after.

Prerequisites

  • A SigNoz Cloudaccount withNozavailable. - Services sending traces and logs to SigNoz.

Step 1: Ask what changed

Open Noz from the top-right header and describe what you saw:

Errors on the checkout service jumped after the 2pm deploy. What changed?

Noz compares checkout's error rate and latency for the windows before and after 2pm and reports what moved: which operations started failing, whether latency shifted, and how the post-deploy window differs from the baseline. Follow up to cut the pre-existing noise:

Show me only the errors that appeared after the deploy and weren't there before.

Step 2: Confirm the cause

Pull a failing trace from after the deploy and show me where it breaks.

Noz pulls a representative post-deploy trace, points to the span that fails or slows down, and offers Suggested Actions to keep going (for example, opening the related logs or the dependency the span calls).

Tips

Anchor on the deploy time. Naming the release window lets Noz compare before and after instead of summarizing the whole window.Verify before you roll back. Treat the proposed cause as a hypothesis until a real failing trace confirms it.

Under the Hood

Under the Hood

To answer, Noz works through several agentic steps, visible under Worked through N steps:

Step What It Did
Ran builder query Compared checkout's error rate for the windows before and after the deploy
Searched traces / logs Pulled the error signatures and failing traces from the post-deploy window
Ran builder query Checked whether latency or a downstream dependency also shifted
Reasoned Isolated what appeared after the release and ranked the likely cause

Next Steps

Find Where Latency Is Going with Noz- When the regression is latency, not errors.Post Deployment Monitoring- Compare metrics before and after a deploy from your coding agent.

If you need help with the steps in this topic, please reach out to us on SigNoz Community Slack.

If you are a SigNoz Cloud user, please use in product chat support located at the bottom right corner of your SigNoz instance or contact us at cloud-support@signoz.io.

── more in #ai-tools 4 stories · sorted by recency
── more on @signoz 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
Live at https://your-agent.zahid.host
Get free account → Pricing
from €0/mo · no card required
LIVE [news/investigate-what-cha…] indexed:0 read:2min 2026-06-14 ·