Use the Diagnostics Console

Overview

The Diagnostics Console is where you go when you want to know exactly what MetaLens360 did and why. Open it from System → Diagnostics. It has three tabs:

Before you start

• Any workspace member can open Diagnostics.
• Activity appears only after something has run. With nothing yet, the log view says "No logs yet — run a sync or comparison to see activity".
• Explain with AI needs a working AI provider. See Configure AI providers.

Steps

Investigate an operation (Activity Timeline)

1. Open the Activity Timeline tab. Counters across the top show RUNNING NOW, SYNCS TODAY, COMPARISONS TODAY, TOTAL OPERATIONS and LAST COMPLETED.
2. Narrow the list with the filters: type (All Types, Syncs, Comparisons, Repo Fetches), status, cloud, org, and the Search… box.
3. Click Expand details on an operation. A sync shows the components retrieved and index stats (Indexed Components, Dependency Edges, Last indexed). A comparison shows Total Components, Drifted, Matching, Missing in Target and Missing in Source. A repo fetch shows commits, pull requests and tags fetched and stored.
4. Click the log icon (Open full log viewer with AI analysis) to read the full execution log.
5. In the log viewer, click Explain with AI for a plain-language summary of what happened and what needs attention. Use Copy visible logs or the export icon to share the log.

Watch the live log (Raw Logs)

1. Open the Raw Logs tab. The stream shows Live while it refreshes.
2. Filter by operation and level, or type in Search messages, context, org….
3. Click Pause live updates to freeze the view while you read; click Resume live to continue.
4. Click Copy visible to copy what's on screen, or Export as .log file to download it.
5. Click Load entire buffer to see older lines, or Clear buffer to start fresh.

Review AI usage (AI Usage & Intelligence)

1. Open the AI Usage & Intelligence tab and pick a window: 7d, 30d or 90d.
2. Read the tiles: Total AI calls, Actual cost, Tokens (in/out), Failures, Active users and Avg latency. Free-tier providers show as free.
3. Check the Provider ledger for each provider's calls, latency, errors, whether it's Available now, Routing now position and Quota left.
4. Scroll to Most-used models, Top AI users, By feature, Recent failures and Call traces to see what each call asked and returned.

Example

Sam's overnight sync of acme-uat shows as failed on Home. He opens Diagnostics, filters to Syncs and acme-uat, expands the failed run and opens the full log. Explain with AI points to an expired session. Sam reconnects the org (see Fix expired org credentials) and reruns the sync. Later, Priya checks AI Usage & Intelligence for 30d and sees that one provider caused most Failures, so she moves it down the fallback order.

FAQs

Does deleting an operation delete my metadata?

No. Deleting sync run records removes the history entries only — "Metadata files are not affected." Deleting comparison jobs removes those comparison results. Both are permanent, so you're asked to Confirm Delete.

Why are some AI calls attributed to "System"?

Scheduled and background work isn't made by a signed-in person, so it's grouped under System.

Do Call traces include my prompts?

Yes, for diagnosis — they show the request sent to the AI provider and its response. Treat exported traces and logs as internal data.

Troubleshooting

"No entries match the current filter"

Clear the search box or reset the filters to All.

Explain with AI fails

No AI provider answered. Check Settings → AI Providers, or see AI provider not configured.

The AI tab shows "Not probed" for a provider

MetaLens360 hasn't tried that provider yet, so its live capacity is unknown. It updates after the next AI call.

Related articles

• Troubleshoot sync failures
• Check sync and fetch status
• Configure AI providers
• Who pays for AI generation