Report a Problem

The fastest way to send useful troubleshooting information is the Report a Problem option in the ChannelWatch Diagnostics tab. It prepares a structured report from inside your running app so you do not have to manually collect screenshots, logs, and debug bundles before asking for help.

Diagnostics and support tools

Diagnostics And Debug Bundle Diagnostics groups health checks, log review, alert tests, and sanitized debug bundle download in one operator surface. Captured from ChannelWatch v0.9.10 with safe demo data.

Note

Report a Problem is operator controlled. ChannelWatch does not send diagnostics automatically, and the report preview is shown before anything is submitted.

When to use it

Use Report a Problem when:

• a notification provider fails, rate-limits, or delivers unexpected content
• Recent Activity, watch history, or delivery history does not match what the DVR is doing
• the dashboard shows a degraded state and you want to include safe diagnostics
• you need to share screenshots or a ChannelWatch-generated debug bundle without putting private files into a public issue body

For quick checks that do not need a report, start with Diagnostics and Common Issues.

Create a report

1. Open ChannelWatch at http://your-server-ip:8501.
2. Go to Diagnostics.
3. Click Report a Problem.
4. Enter the problem summary and what you expected to happen.
5. Review the generated public issue preview.
6. Attach screenshots if they help explain the issue.
7. Create or attach one ChannelWatch debug bundle ZIP when the report asks for it.
8. Submit the report, or use the support code/offline package if direct submit is not available.

What goes into the public issue

The public issue preview is intentionally limited to details that are safe to discuss in the tracker:

Field	Purpose
Problem summary	What is wrong from the operator's point of view
Expected behavior	What should have happened instead
Public contact handles	Optional GitHub or Channels community usernames
Diagnostics summary	ChannelWatch version, DVR counts, core status, monitoring status, enabled alert toggles, and provider names

What stays private

Screenshots and debug bundle ZIPs are private support attachments. They are not placed into the public issue body.

ChannelWatch also keeps these out of the public issue text:

• private email address
• screenshot filenames
• raw logs
• API keys
• webhook secrets
• notification provider credentials
• DVR API keys
• private config values

Caution

Review screenshots before attaching them. ChannelWatch validates file type and size, but only you know whether a screenshot shows private channels, names, addresses, or browser details you do not want to share.

Direct submit and manual upload

When direct submit is available, the app sends the sanitized report through the configured support intake path.

If direct submit is not available, ChannelWatch can create a support code or offline package. The hosted upload page at /report accepts that support code, lets you add screenshots or one debug bundle, and re-validates everything before creating the public issue or sending private attachments.

The in-app flow does not show a hosted bot-verification challenge. The public upload page keeps its own verification and support-code gate because it is reachable from the public web.

Related pages

• Diagnostics - run tests and open Report a Problem
• Debug Bundles - what the debug bundle contains and excludes
• Privacy - local artifacts, outbound traffic, and support-report boundaries
• Common Issues - fixes to try before filing a report