SigSentry Documentation

Install the SigSentry Slack app to run analyses from any channel using /sigsentry analyze. Threaded follow-ups continue the analysis in the same Slack thread.

Prerequisites

Need	Notes
Slack workspace	Permission to install apps
At least one project in SigSentry	Logs and (optionally) repos connected

Setup walkthrough

Click "Install Slack" in SigSentry

Go to Settings → Integrations → Slack → Install. You'll be redirected to Slack's OAuth consent flow.

Authorize the requested scopes

The SigSentry Slack app requests:

Scope	Why
`commands`	Receive `/sigsentry` slash commands
`chat:write`	Post analysis results back to threads
`users:read`, `users:read.email`	Identity-map Slack users to SigSentry users
`channels:history`, `groups:history`, `im:history`	Read thread context for follow-ups

Click Allow.

Return to SigSentry

You're redirected back to the dashboard. The connected workspace is listed under Settings → Integrations → Connected workspaces, with the name of the workspace and who installed it.

Run a test command

In any Slack channel where the SigSentry app is present, type:

/sigsentry analyze test smoke last 1 hour

After 30–60 seconds, the diagnosis posts as a threaded reply.

Available commands

/sigsentry analyze <description> <time-expression> [--project=<slug>]
/sigsentry help
/sigsentry projects

See Command grammar for the full grammar including time expressions like last 30 minutes, since 9am, etc.

How threading works

When you run /sigsentry analyze, the response posts as a new thread in the channel. Subsequent messages in that thread are treated as follow-up questions:

You: /sigsentry analyze checkout 500s last 30m
Bot: [posts diagnosis]
You: What changed in the last hour?
Bot: [follow-up answer]
You: Is PR #482 related?
Bot: [follow-up answer]

Follow-ups continue the original analysis context — no need to re-state details.

The user who runs /sigsentry analyze is matched to a SigSentry user by email. If your Slack profile email doesn't match your SigSentry account, the analysis still runs but is attributed to the workspace installer.

To restrict who can trigger analyses on which project, configure the project access list.

Default project resolution

Without --project=<slug>, the bot picks the default project for your tenant. Override per-channel by adding the project ID under that channel's Channels binding in Settings → Integrations.

Resolution priority	Source
1	`--project=<slug>` flag
2	Channel-level binding (per Slack channel)
3	Tenant default project

Revoking access

To revoke SigSentry's Slack access:

For	Action
Whole workspace	Slack admin → Apps → SigSentry → Uninstall
Specific channel	Remove the SigSentry app from that channel

You can also disconnect from the SigSentry side under Settings → Integrations → Connected workspaces → Disconnect.

Troubleshooting

Symptom	Likely cause
`/sigsentry` not recognized	App not installed in workspace, or installed but not added to that channel
"User not authorized" response	Project access list excludes you, or your Slack email doesn't match a SigSentry user
Slow responses	Long-running analyses over large log windows; widen workspace concurrency or narrow time
Follow-ups not threading	Slack scopes missing — re-authorize to grant `channels:history` etc.

Slack