Find and fix broken Analytics and App Logs setup

An empty dashboard can mean no traffic or a missing tracker. An integration pointing at the wrong destination can also cause missing data. Setup Health checks the source of an eligible local workspace for specific mistakes. Use it when you enable Analytics or App Logs, and revisit it after changing installation code or dependencies.

Findings appear in Needs attention on the workspace home and in the collapsible sidebar card. Settings → Analytics and Settings → App Logs also show warnings for their respective findings. These surfaces share the active workspace’s scan state. Central pages do not run or display this scan.

Analytics tracker is missing means Analytics is enabled for the workspace. The scan found no supported tracker tag or programmatic configuration. Choose Fix with agent to start a thread with the exact tag. Ask it to add the integration to the right app shell. Copy snippet lets you install the tag yourself.

Analytics site ID does not match means a literal data-site-id differs from this workspace’s assigned tracking ID. Fix with agent receives the assigned ID and corrected tag. Dynamic IDs are not treated as mismatches. The absence of this finding does not prove a dynamically resolved value is correct.

Analytics uses a public tracking ID and an allowed domain. Do not substitute the secret project key used by App Logs and Feedback. Review the tag in the intended application shell and confirm that its domain matches the deployed site.

Analytics collector is proxied identifies a non-Aiola data-host-url, rewrite, redirect, route, or proxy that forwards collection through another server. That proxy hides the visitor connection, losing trustworthy country and city information. The collector should receive events directly at https://aiola.app/api/collect.

Fix with agent asks for removal of the collector rewrite or proxy and data-host-url while retaining the cdn.aiola.app/analytics.js script. A proxy serving the script itself may remain. Distinguish downloading JavaScript from sending events: the finding concerns the collector’s connection. The proxy check is skipped for aiola.app and its subdomains.

App Logs SDK is outdated means a workspace package lists an older @aiolaapp/logger version. Its installed or locked semantic version is older than npm’s latest version. The finding shows the current and latest versions and provides Update to v<latest>.

The updater runs the detected package manager in the package directory. npm uses install @aiolaapp/logger@latest; pnpm, yarn, and bun use add @aiolaapp/logger@latest. The directory must sit inside the workspace. Its package.json must list the logger in dependencies or devDependencies.

The command can run for up to five minutes and returns the last 40 output lines. Afterward, inspect the dependency and lockfile diff, read the command result, and run the application’s relevant checks. A successful update triggers a rescan; use that result to see whether the version finding cleared.

App Logs uses a legacy endpoint is a separate error from an outdated package. It identifies an endpoint option or AIOLA_ENDPOINT value containing app.aiola.com or /functions/v1/app-logs-ingest. Updating a dependency alone may leave that hardcoded configuration in place.

Fix with agent asks the thread to use https://aiola.app/api/app-logs-ingest or remove the endpoint option so the SDK default applies. Review the proposed change in the affected file and keep the correct project key configuration. Confirm the application still initializes the logger. Then run Check again.

Findings have no dismiss action. Check again forces a fresh workspace scan and clears the cached npm-latest version before checking. A finding disappears when the new scan no longer detects it. Starting a fix thread alone does not clear the warning.

The renderer normally scans once per workspace per app process, with no interval or focus polling. Workspace results and npm version lookups are cached for one hour. The disk scan has size and file-count limits. It excludes dependencies, build output, Git data, tests, fixtures, and the bundled analytics.js file. Treat a clean scan as the absence of supported findings, then verify actual collection in your deployed application.

Sign in to an account with Pro Monthly, Pro Yearly, or an active trial. Open a local workspace with a root path. SSH workspaces and Central routes are skipped. GUI Lifetime alone does not enable Setup Health. Analytics is checked only when the workspace has an Analytics site. App Logs requires a project key and logs not explicitly disabled.

Skipped results contain no findings. If nothing appears, check eligibility and integration configuration before assuming the scan ran. See the Setup Health documentation for the full scan contract. The download is free. The seven-day trial requires a payment card and is limited to eligible first-time customers choosing Pro Monthly 100k.