Dashboard Analytics

The analytics dashboard gives a bird's-eye view of your project health. All metrics update in real-time as bugs are submitted, updated, and resolved by your team.

Access the analytics dashboard from the main Dashboard tab in your project. The following metrics are displayed at a glance:

• Bug count by status — see how many bugs are open, in_progress, resolved, closed, or wont_fix
• Bug count by priority — breakdown across critical, high, medium, and low priorities
• Bug count by category — distribution across gameplay, visual, audio, crash, performance, and custom categories
• Bug trend over time — a 30-day chart showing new bugs filed, resolved, and net change per day
• Team member activity metrics — bugs assigned, resolved, and commented on per team member
• Recent activity feed — a live stream of the latest actions across all bugs in the project

Data updates in real-time as bugs are submitted and updated, so the dashboard always reflects the current state of your project.

Crash Analytics & Session Tracking

Bugnet SDKs automatically track game sessions and crash events, giving you deep visibility into your game's stability across platforms and versions.

How It Works

1. Session Start — When the game launches, the SDK calls POST /api/sessions/start with a unique session token, platform, game version, and device info.
2. Crash Detection — On an uncaught error or crash, the SDK marks the session as crashed via POST /api/sessions/end with crashed: true.
3. Clean Exit — On normal shutdown, the SDK calls the same endpoint with crashed: false.

Key Metrics

• Crash-Free Rate — Percentage of sessions without a crash. Target: 99.5%+.
• Daily Trend — 30-day chart of crash-free rate over time.
• Platform Breakdown — Crash rates by platform (Windows, Mac, Linux, iOS, Android).
• Version Comparison — Compare crash rates across game versions to spot regressions.
• Top Crash Signatures — Most frequent crashes grouped by fingerprint for faster debugging.

Custom Engine Integration

If you are using a custom engine without an official SDK, you can integrate session tracking directly via the REST API:

# Start a session
POST /api/sessions/start
{"api_key":"sk_live_...","session_token":"unique-id","platform":"Windows","game_version":"1.2.0"}

# End a session (clean exit)
POST /api/sessions/end
{"api_key":"sk_live_...","session_token":"unique-id","crashed":false}

# End a session (crash detected)
POST /api/sessions/end
{"api_key":"sk_live_...","session_token":"unique-id","crashed":true}

View crash analytics in the Game Health dashboard tab.

Session Replays

Record and replay player sessions leading up to a crash or bug report. Session replays capture mouse movement, clicks, and key presses, making it easy to reproduce issues without guessing what the player was doing.

How It Works

1. Enable session capture in your project settings (requires Studio or AAA plan)
2. The SDK automatically starts recording input events on initialization
3. When a bug report is submitted, replay data is sent to POST /api/session-replays
4. View the replay in the bug detail panel in your dashboard

What Gets Recorded

• Mouse movement — position tracked at 50ms intervals with screen dimensions
• Mouse clicks — position and timestamp of each click
• Key presses — key name and timestamp (Web, Unity, Godot SDKs)
• Scroll & resize — viewport changes (Web SDK only)

Events are capped at 5,000 per session to keep payloads lightweight. All four SDKs (Web, Unity, Godot, Unreal) support session replays.

Plan Enforcement

Session replays are only available on paid plans (Studio and AAA). The server enforces this in two ways:

• The GET /api/bugs/settings endpoint returns session_capture: false for free-plan projects, so SDKs never start recording
• The POST /api/session-replays endpoint rejects submissions from projects owned by free-plan users

Release Health Monitor

Monitor the health of each game version at a glance. The Release Health dashboard helps you quickly identify problematic releases and prioritize hotfixes.

Per-Version Metrics

• Total bugs reported — all bugs filed against this version
• Open vs resolved count — how many remain unresolved
• Crash rate — percentage of sessions that ended in a crash
• Health score (0–100) — composite score based on crash rate, bug volume, and resolution speed
• Letter grade (A through F) — quick visual indicator of release quality
• First and latest report timestamps — when bugs started and when the most recent one arrived

API Endpoints

Performance Profiling

Capture detailed performance metrics alongside bug reports. Performance snapshots help you correlate bugs with hardware bottlenecks, frame drops, and resource spikes.

Available on the Studio plan and above.

Metrics Captured

• FPS — frames per second at the time of the report
• Frame time — time per frame in milliseconds
• Memory usage — current memory consumption in MB
• GPU usage — GPU utilization percentage
• CPU usage — CPU utilization percentage
• Draw calls — number of draw calls in the current frame
• Triangle count — total triangles rendered
• Network latency — round-trip time in milliseconds (for multiplayer games)
• Custom metrics — game-specific values you define (e.g., entity count, AI tick time)

Performance snapshots are attached to individual bug reports. You can also view the project-wide performance summary for trend analysis across all reports.

Submit performance data automatically via the SDK, or manually via the API:

Regression Detection

Bugnet automatically detects bugs that match patterns from previously resolved issues, helping you catch bugs that were supposed to be fixed.

How It Works

1. When a new bug is filed, Bugnet compares it against resolved bugs in the same project.
2. If the category, keywords, or crash signature match a previously resolved bug, a regression is flagged.
3. Your team reviews and either confirms or dismisses the regression.

Regression States

API Endpoints

Satisfaction Ratings

Collect player satisfaction ratings after bugs are resolved. Satisfaction data helps you identify areas where bug resolution quality needs improvement and track team performance over time.

How It Works

• After a bug is resolved, the player can rate their experience on a 1–5 star scale.
• An optional comment can be submitted alongside the rating.
• Ratings are aggregated into a project-level satisfaction summary.

Project-Level Summary

• Average rating — mean satisfaction score across all rated bugs
• Rating distribution — breakdown of 1-star through 5-star counts
• Trend over time — how satisfaction scores change week over week

API Endpoints

API Usage

Monitor your API usage and consumption to plan capacity and identify usage patterns. API usage metrics are accessible from the Integrate tab in your project dashboard.

Metrics Available

• Bug submissions — count of bugs submitted in the last 7 and 30 days
• Session starts — count of game sessions started in the last 7 and 30 days
• Total API calls — aggregate API call volume across all endpoints
• Per-endpoint breakdown — see which endpoints are called most frequently

Use this data to plan capacity, identify usage patterns, and ensure you stay within your plan limits.

Alert Rules

Configure automated alerts based on metric thresholds. When a threshold is breached, Bugnet triggers email notifications and webhook events so your team can respond quickly.

Alert Types

Configuration Options

• Metric to monitor — select the metric that triggers the alert
• Threshold value — the value that must be exceeded (or dropped below) to fire
• Time window — evaluation period in hours (e.g., 1, 6, 24)
• Enable/disable toggle — temporarily silence an alert without deleting it

Alerts can trigger email notifications and webhook events, allowing you to integrate with Discord, Slack, PagerDuty, or any HTTP endpoint.

API Endpoints

Auto-Triage

Bugnet's AI-powered auto-triage analyzes incoming bug reports and provides intelligent prioritization, categorization, and response suggestions.

Available on the Studio plan and above.

Capabilities

• Auto-categorize bugs — automatically assign a category based on the title and description content
• Suggest priority — recommend a priority level based on severity indicators and potential impact
• Generate response templates — draft suggested responses to send to the reporting player
• Group similar crashes — cluster crashes by signature to reduce noise and surface root causes
• Churn risk scoring — flag players at risk of leaving based on sentiment analysis and behavior patterns

Access auto-triage from the Bugs dashboard or trigger it programmatically via the API: