Triage a Customer-Reported Issue with Noz

SigNoz Cloud - This page applies to SigNoz Cloud editions.

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 Cloud account with Noz available.
  • Logs that carry a tenant or user identifier (for example, tenant or user_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

  1. Match your attribute. Use the field your logs actually carry (tenant, customer_id, user_id) so the filter resolves.
  2. 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

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

StepWhat It Did
Ran builder queryCounted errors for the tenant against the whole service
Searched logsFiltered logs to the tenant or user attribute over the window
ReasonedJudged whether the issue was isolated and summarized the shared cause

Next Steps

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.

Last updated: June 14, 2026

Edit on GitHub

Was this page helpful?

Your response helps us improve this page.

On this page

Is this page helpful?

Your response helps us improve this page.