Diagnostics and logs

A diagnostics export helps support understand your installation without access to your tenant. Kairavo writes it to a ZIP file on your computer. Nothing is uploaded. You decide whether to send it.

Export diagnosticsCopy Anchor Link

What the ZIP containsCopy Anchor Link

diagnostics.json holds only fields from a fixed list:

• App: the Kairavo version, the Node, Electron and Chromium versions, the operating system and processor architecture, and whether this is an installed build.
• Database: the local database state, the applied database migrations, an approximate row count per table, whether you use a custom database folder, and whether the Visual C++ runtime is missing.
• Collection: whether collection runs, and for each data source the number of tenants and how many are healthy, collecting, stale, unavailable or failing, with the oldest and newest successful run. It also counts observation gaps of the last 30 days.
• Settings: your choices under Startup and updates, whether a policy manages automatic updates, the update state, whether operating system encryption is available, and the number of signed-in tenants.
• Integrations: each kind of configured integration, such as alert delivery or AI model endpoints, with the number of saved secrets for it. No names, URLs or hosts.
• License: whether a key is saved, whether the last check was offline, the number of licensed and read-only tenants, and the verification dates.

What is never includedCopy Anchor Link

• Tenant IDs, tenant names, account names, device or user data, or any collected history.
• Your license key, not even part of it.
• Sign-in tokens, database passwords or integration secret values.
• URLs, host names or folder paths.
• Error messages from collection, since they can contain names from your tenant.

How secrets are scrubbed from logsCopy Anchor Link

Every log line is scrubbed before it is written to disk. Tokens, keys, Authorization headers, JWTs, certificates and license keys never reach the log file.

When you include log lines in an export, Kairavo takes the last 512 KB of the current log file and scrubs it again. This second pass also removes:

• Every saved integration secret value.
• Connection strings and passwords in them.
• URLs to your own hosts. Links to Microsoft sign-in, Microsoft Graph, GitHub, kairavo.com and 127.0.0.1 keep their path, without the query.
• Home folder names, such as C:\Users\<name> and /Users/<name>.
• Host names in network errors, and IP addresses other than loopback.
• Email addresses and user principal names.
• Identifiers such as tenant, device and object IDs. They become [id]. A line with more than three identifiers is removed completely.

If the export would still contain a saved secret value, Kairavo stops and shows: "The export was stopped because it would have contained a secret. Export without logs, or contact support."

Send it to supportCopy Anchor Link

Select Compose email under Support and diagnostics. Your email app opens a message to support@ugurlabs.com with the subject "Kairavo support request" and your app version.

The email has no attachment. Describe what happened, what you expected and when it started. Then attach the diagnostics ZIP yourself, if it helps.

Where logs liveCopy Anchor Link

Kairavo writes its log to local files. They are never uploaded. To open the folder, go to Preferences, scroll to About and select Open logs folder.

%APPDATA%\Kairavo\logs

How logs rotateCopy Anchor Link

• The current log is main.log.
• When it reaches 5 MB, it becomes main.1.log, the previous main.1.log becomes main.2.log, and so on.
• Kairavo keeps five files: main.log and main.1.log to main.4.log. The oldest file is deleted. The logs never use more than about 25 MB.