01
Connect your application
Production failures need a route back to your workspace. Generate a project key in Settings, under API Key, then connect JavaScript, Python, or HTTP collection.
Aiola App Logs
Put errors on
a fix path.
Production errors pile up without a clear path back to the code. Aiola groups failures with stacks and breadcrumbs, then opens agent threads with that context. Investigate the cause and review proposed fixes beside your project.
How it works
02
Inspect grouped issues
Repeated errors make individual failures hard to spot. Refresh grouped issues to inspect counts, first occurrence, last occurrence, and individual events.
03
Chat, Open chat, or Fix it
An error report alone does not explain the fix. Chat starts investigations; Open chat resumes them, while Fix it sends error context into the thread.
Inspect and triage errors
Stack traces
Minified errors hide the failing code. Stack traces show exception types, functions, files, lines, and source context when matching source maps exist.
Combined project inbox
Checking each repository for failures takes time. Central App Logs combines workspace issues while retaining their project context.
Breadcrumbs
Reproducing a failure requires knowing what happened first. Breadcrumbs show console messages, clicks, navigation, and requests before the error.
Request and runtime context
Some failures only affect particular requests or devices. Event details show supplied request, user, browser, operating system, device, runtime, environment, and release context.
Releases and source maps
A deployed error needs the source from that release. Upload matching source maps and browse or delete release uploads in settings.
Issue statuses
Unsorted errors make follow-up work hard to track. Set Open, In Progress, Human Review, Closed, or Ignored individually or in bulk.
Error totals and trends
You need to see whether failures are increasing. Totals and trend sparklines summarize events, errors, warnings, and unique issues.
Search and filters
A noisy inbox hides the failures affecting your users. Search issues and filter status, time, severity, environment, browser, operating system, device, country, or HTTP status.
Copy and delete
Some investigations need a copy, while obsolete issues need clearing. Copy issue details or delete individual issues and selected groups with their events.
Configure collection and agent actions
SDKs and raw HTTP
Writing collection code from scratch slows setup. Copy JavaScript, Python, or HTTP examples, or start an Add to App installation thread.
Custom analysis and fix prompts
Repeating investigation instructions wastes time. Settings, under Instructions, saves App Logs analysis and fix prompts for new action threads.
Local or Worktree
An error fix can interfere with your current checkout. Settings, under Git, lets App Logs actions start in a fresh worktree.
Automatic issue retention
Closed issues should not fill the inbox forever. Aiola removes closed groups after 30 days without events and keeps ignored groups.
Project key lifecycle
A leaked integration key needs replacing. Generate and copy the shared App Logs and Feedback key once, check Last used, regenerate, or revoke.
Setup Health
An outdated logger can leave gaps in error collection. Setup Health checks keyed local workspaces, offers updates or agent fixes, and rescans.
Problems Aiola solves here
The same failure buries your inbox. Grouped issues combine matching events and preserve counts and occurrence times.
A stack trace alone does not reproduce the bug. Breadcrumbs and request context show supplied events leading to the failure. Release source maps reveal original code locations.
Copying errors into a coding assistant loses context. Chat starts an investigation with issue details; Open chat resumes it. Fix it sends context into the issue’s thread.
Old integrations can stop collecting useful errors. Setup Health checks logger installation in local workspaces with a project key. Use version updates, agent fixes, and Check again.
You need to distinguish a fixed error from an ignored one. Issue statuses track progress, and new occurrences reopen closed groups. Automatic retention removes inactive closed groups after 30 days, while ignored groups remain.
Keep the integration healthy
Use @aiolaapp/logger for JavaScript runtimes or the aiola Python package. Other runtimes can post JSON to https://aiola.app/api/app-logs-ingest.
Use Settings, then API Key, to generate a missing key. Copy it when generated; its full value is shown once.
Regeneration replaces the previous key, so update your application's configuration. Revocation stops senders that use that key.
Setup Health scans local workspaces with an existing project key and enabled logging. Missing keys skip the logger scan.
Update outdated loggers with the version update action. Legacy endpoint findings offer Fix with agent; Check again rescans after corrections.
Follow the App Logs setup guide. Hosted App Logs needs Pro or the 7-day trial.
Common questions
Build, ship and fix in one app
Errors, user feedback, GitHub and analytics live next to your coding agents in one desktop app. Every issue becomes a task an agent can take.