Sending us a log

Logs turn "it didn't work" into something we can act on. Send the logs folder on its own, or — when we can't reproduce what you're seeing — more of your data directory, knowing exactly what that shares.

Start here: the logs folder

Inside your data directory is a logs folder, with one timestamped file per launch. Zip the whole folder and attach it — it's small, and it's what we read first.

Windows%LOCALAPPDATA%\ProtoSorcery\Scryglass\data\logs
macOS~/Library/Application Support/com.protosorcery.scryglass/data/logs
Linux~/.local/share/Scryglass/data/logs

Tell us your OS version and what you were doing in the same email. Between that and the log, most problems don't need a second round of questions.

When we ask for more: the data directory

Some problems only make sense with your configuration in front of us — a device that won't map, a dashboard that renders wrong. For those, zip the whole data directory except the disk cache, which is large and tells us nothing:

exclude:  data/user/disk_cache

This shares more than a log does: your channel names, device mappings, dashboard layouts and settings travel with it. Those can carry project details you'd rather keep private. Send it only when we've asked, and only if you're comfortable — the logs folder alone is always a valid answer.

Either way, it's an ordinary zip going to a person by email. We read it, we fix the thing, and we don't keep it longer than that takes.

Still stuck? Send your version number — it's under the System button at the top right of the app — and what you were doing. Replies come from the team that builds the app.

support⁠[at]⁠protosorcery.com
BETA · PHASE 1

Ask for an invitation

Five questions. They decide which phase you land in — we open to a few kinds of user at a time so support stays fast.

What's your work?
How many people would use it?
Which platform?
Would this be personal or paid work?
No newsletter. We write once, when your phase opens.