cd /news/ai-tools/triage-a-customer-reported-issue-wit… · home topics ai-tools article
[ARTICLE · art-29932] src=signoz.io ↗ pub= topic=ai-tools verified=true sentiment=· neutral

Triage a Customer-Reported Issue with Noz

SigNoz released a guide for using its AI assistant Noz to triage customer-reported issues, such as 500 errors on upload, by checking blast radius and pulling error logs. The tool helps engineers determine if an issue is isolated to one tenant or widespread, and provides suggested actions for further investigation.

read2 min views5 publishedJun 14, 2026

A customer opened a ticket: they are seeing 500s on upload. Before you escalate, you ask Noz whether it is just them or a wider problem, and pull their errors.

Prerequisites

  • A SigNoz Cloudaccount withNozavailable. - Logs that carry a tenant or user identifier (for example, tenant

oruser_id

).

Step 1: Find the blast radius

Open Noz from the top-right header and ask whether the issue is isolated:

Is tenant acme-corp seeing errors right now, or is everyone?

Noz counts errors for that tenant against the rest of the service and tells you whether the problem is scoped to one customer or hitting everyone, which decides how you escalate.

Step 2: Pull the customer's errors and find the pattern

Show me the error logs for user_id 48213 in the last hour, grouped by endpoint.

Noz filters logs to that identifier and summarizes what links them, for example a single failing endpoint or a common status code, so you have the exact failures the customer hit and the shared cause, with Suggested Actions to pull a failing trace or widen the search.

Tips

Match your attribute. Use the field your logs actually carry (tenant

,customer_id

,user_id

) so the filter resolves.Bridge to a trace. Once you have the failing logs, ask Noz to pull the trace for one of them to see the full request path.

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 Counted errors for the tenant against the whole service
Searched logs Filtered logs to the tenant or user attribute over the window
Reasoned Judged whether the issue was isolated and summarized the shared cause

Next Steps

Investigate What Changed After a Deploy with Noz- When the issue turns out to be widespread.Natural Language Log Exploration- Run the same log search 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/triage-a-customer-re…] indexed:0 read:2min 2026-06-14 ·