AllStak Troubleshooting Guides
Step-by-step fixes for common AllStak setup issues: events not showing, API keys, source maps, OpenTelemetry, Slack alerts, agent connectivity, and more.
Events not showing in AllStak: diagnose it in minutes
Your SDK is installed but the dashboard stays empty, or new errors stop arriving. Almost every case comes down to one of six checks below.
Invalid API key: find the bad key in minutes
The SDK rejects your key, ingest returns auth errors, or events silently vanish. The fix is almost always one of four key-handling mistakes.
Source maps not resolving: get readable stack traces back
Your JavaScript errors show minified frames like a.js:1:48213 instead of your source files. Nine times out of ten, the release strings do not match.
Events without stack traces: get the frames back
Errors arrive in AllStak as bare messages with no frames to debug from. The cause is almost always in how the error was thrown or captured.
OpenTelemetry traces not appearing: check the exporter first
Your services are instrumented with OTel but AllStak shows no spans. The usual culprit is a gRPC exporter, a wrong endpoint, or a missing flush.
Slack alerts not arriving: trace the route in minutes
Errors fire in AllStak but nothing lands in your Slack channel. The route has exactly three links — the connection, the rule, and the channel — and one of them is broken.
Jira issues not creating: fix the connection, then the permissions
Creating a Jira issue from an AllStak error fails, or closing the Jira issue never resolves the linked error. Both have short, specific checklists.
Linux agent not connecting: diagnose it from the host
You installed the agent but the server never appears in the fleet — or it appears and immediately goes silent. Everything you need is in systemctl and journalctl.
Host gone stale in the fleet: find out why
The host exists in your fleet view but its data stopped updating. Start with the last-seen timestamp — it tells you which class of failure you have.
Events arriving without a release: wire it up properly
Errors arrive untagged, or every deploy shows the same release. The SDK only tags events with the release you set — here is how to set it right.