DevTools Documentation

Troubleshooting

Cloud logging, MCP integrations, frontend tooling, and SSH workflows for production DevTools teams.

Account Settings Resources MCP Servers GitHub SDK Repo
MCP Access
Cloud Logger
Frontend Tools
SSH Ready
DevTools Docs
Start
Overview
SDK
SDKs (Python + Node)
Platform
Overview API Keys Resources Logging MCP Servers Frontend & SSH
Help
Troubleshooting
Troubleshooting

Most issues come from key scope, user headers, resource identifiers, or disconnected GitHub auth.

Logs not appearing in timeline
  • Verify ALSHIVAL_USERNAME, ALSHIVAL_API_KEY, and ALSHIVAL_RESOURCE.
  • Copy ALSHIVAL_RESOURCE from DevTools Resource Details -> Resource URL for the exact target resource (owned or shared).
  • Confirm the resource belongs to the same DevTools account as the key.
  • Enable ALSHIVAL_DEBUG=true temporarily in SDK flows.
  • Run the curl ingest test from the logging docs to isolate SDK vs network issues.
MCP tools are missing
  • Send X-User-Username with your X-API-Key.
  • Use the MCP tools/list curl check from MCP Servers.
  • Check that your account has the expected DevTools access tier.
  • For GitHub MCP, verify your GitHub account is connected in DevTools.
GitHub MCP auth failures

Common causes:

  • Missing X-User-Username or mismatch with key owner.
  • No active GitHub social connection on your DevTools account.
  • Using a stale key after rotation.
SSH issues
  • Confirm private key path and permissions (chmod 600).
  • Confirm target host/user values from DevTools Resource Details.
  • Validate network path, security groups, and IP allowlists.
Minimal Health Checks
python -m pip show alshival

curl -sS https://mcp.alshival.ai/mcp/ \
  -H "Content-Type: application/json" \
  -H "X-API-Key: $ALSHIVAL_API_KEY" \
  -H "X-User-Username: $ALSHIVAL_USERNAME" \
  -d '{"jsonrpc":"2.0","id":"1","method":"tools/list","params":{}}'