Data handling
What SigSentry stores, what it doesn't, and where to look when an analysis isn't behaving as expected
This page covers the questions teams typically ask before adopting SigSentry: where their data goes, what's persisted, and what's not.
What we keep vs what we don't
| Type | Stored? |
|---|---|
| Analysis result (diagnosis) | ✅ — your audit trail and historical data |
| Description, time window, metadata | ✅ |
| Logs that were fetched | ❌ — your raw logs stay in your log aggregator |
| Repo file contents | ❌ — fetched on demand only |
Your raw logs stay in the log aggregator you already use. SigSentry reads them only for the duration of an analysis. For full data-handling details, see our Privacy Policy.
Where to look when something's off
| Symptom | Where to look |
|---|---|
403 QUOTA_EXCEEDED | Plans & quotas — enable overage if needed |
| "No logs found" | Log sources troubleshooting — usually a time-window or scope issue |
| Analysis stuck | Usually transient. If persistent, see Troubleshooting |
| Wrong severity assigned | Improve project AI context |
| Code correlation missing | Verify your repo is connected and service mappings match log fields |
| Notifications not arriving | Check the channel's severity threshold and credentials |