Skip to main content

​
Integration Issues

Ensure @Struct is invited to the channel and the Slack integration is connected in Connections. Struct can only monitor and respond in channels where it has been explicitly invited.
Check that your alerting source (Sentry, Datadog) is connected in Connections and the correct projects/services are selected. For issue tracker triggers (Linear), ensure the issue is assigned to Struct or Struct is @tagged in a comment.
Go to Connections → GitHub → Manage Repositories and ensure the repo is selected. Some organizations require admin approval for third-party apps.
Verify your cloud log provider credentials have sufficient read permissions. Check that the correct region, log group, or workspace is configured. See Connections for setup details.
Verify the Sentry organization is selected in Connections → Sentry and your token has read access to the relevant projects.
Double-check that API keys or credentials have the required read permissions. For Grafana, ensure the API key has at least Viewer access. For Datadog, ensure both API and application keys are provided, and that the application key’s role grants the logs_read_data, timeseries_query, monitors_read, and dashboards_read scopes. A 403 Forbidden on metric queries specifically (while logs work) usually means the role is missing timeseries_query.

​
Investigation Issues

Normal investigation time is under 5 minutes. Complex issues with large codebases or many log sources may take longer. Check the Struct dashboard for status. If investigations consistently take too long, try narrowing the scope of connected log sources.
The more integrations connected, the richer the investigation. Ensure relevant observability platforms and cloud log providers are connected. Struct produces the best results when it can cross-reference multiple signal sources.
Struct improves over time as it processes more alerts. Ensure all relevant data sources are connected. You can ask follow-up questions in the Slack thread to refine the analysis—Struct maintains full context throughout the conversation.
Check that GitHub is connected with write access. Common causes: branch protection rules, signed commit requirements, or permissions issues. Try reconnecting GitHub in Connections.
Struct runs your existing test suite via configured scripts. Review the test output in the PR and request changes if needed.

​
MCP & CLI Bridge Issues

Verify you ran the correct install command from Settings → Coding Agent → Claude Code. The command should look like:
claude mcp add --transport http struct <your-mcp-url>
Make sure you’re using the MCP URL shown in your settings page, and that you’ve logged in with struct login at least once.
Try the one-click install button in Settings → Coding Agent → Cursor. If that doesn’t work, manually add the config to .cursor/mcp.json:
{
  "mcpServers": {
    "struct": {
      "url": "<your-mcp-url>"
    }
  }
}
You can find your MCP URL in Settings → Coding Agent → Cursor.
OAuth login is triggered automatically on first MCP tool use. If authentication fails, try running struct login from your terminal to re-authenticate, then retry in your coding agent.
This requires the CLI bridge to be installed. Run:
npm install -g @struct/cli
struct bridge install
If you’ve already installed it, try struct bridge uninstall followed by struct bridge install to re-register the protocol handler.
Ensure the CLI is installed globally:
npm install -g @struct/cli
If you use nvm, fnm, or another Node version manager, make sure the global bin directory is in your PATH. Try opening a new terminal window after installation.
On macOS, the bridge registers as a native app. Try restarting your browser after installation. If using Chrome, you may need to allow the struct:// protocol when prompted.On Linux, ensure xdg-mime is available and the .desktop file was created correctly. Run struct bridge install again to re-register.

​
FAQ

Struct is an AI support engineer that automatically investigates on-call engineering alerts. It cross-references logs, metrics, traces, and the codebase to determine root cause, assess impact, and suggest fixes — before you start debugging.
Struct offers a free plan that includes monthly credits so you can start investigating immediately — no credit card required. You can upgrade to a paid plan anytime for more credits and higher limits. See Usage & Credits for details.
Credits are consumed when Struct runs investigations. Your plan includes a monthly credit allowance that resets each billing cycle. You can also purchase top-up credits that roll over indefinitely. See Usage & Credits for details.
Ask Struct is a natural language interface for querying your production systems. Ask about alerts, logs, metrics, or code — and Struct gathers context across your connected tools to deliver answers. Try it at Ask Struct. See Ask Struct for more.
Go to Settings → Coding Agent in the web app and follow the instructions for your coding agent (Claude Code or Cursor). See Open in Claude Code / Cursor for details.
Run npm install -g @struct/cli then struct bridge install. This enables one-click “Open in” buttons from the web app. See Open in Claude Code / Cursor for details.
General-purpose coding agents require manual log retrieval, custom orchestration, and observability integration to debug production issues.Struct is already integrated with your observability stack. It automatically collects production data, builds structured investigations, maintains historical intelligence, and provides secure tenant isolation.Struct investigates. Coding agents implement. They are complementary—Struct provides the production-grounded context, and coding agents generate the code.
Yes. Struct builds on-call intelligence from past alerts and investigations, enabling pattern recognition and faster root cause detection. The more issues it processes, the more accurate investigations become.
Yes. After an investigation, you can approve a fix and the Struct Build Agent will create a branch, implement the changes, run tests, and open a PR. You can also open in Claude Code or Cursor with full investigation context.
No. Code is read during analysis but not permanently stored. All data is encrypted and logically isolated per customer. Struct is SOC2 Type II and HIPAA compliant.
Struct integrates with Sentry, Datadog, Grafana, Prometheus, Loki, SumoLogic, Render, AWS CloudWatch, Azure Monitor, Google Cloud Logging, Slack, Linear, Asana, and GitHub. New integrations can be built in days.
You can be up and running in under 5 minutes with the free plan. Connect GitHub, connect Slack, and start investigating.
  • Engineering teams with on-call rotations
  • Teams with heavy alert loads
  • Organizations wanting automated root cause analysis
  • Teams using coding agents who want structured production context
  • Companies where uptime and reliability are critical (fintech, payments, healthcare, etc.)
Currently GitHub only. Other providers are on the roadmap.
Go to the investigation in the Struct dashboard and click Cancel.

​
Contact Support

Email us at [email protected]