Troubleshooting
Common integration issues and how to fix them.
No events in the dashboard
| Check | Action |
|---|---|
| SDK key | Copy fresh key from Settings; must start with am_ |
| Environment | Confirm AMLEXIA_SDK_KEY is set in the running process (not only .env locally) |
| Ingest URL | Default https://ingest.amlexia.com — typo-free |
| Shutdown | Call client.shutdown() or flush() so buffered events send |
| Time | Allow ~1 minute; refresh Overview or Live |
Test ingest health:
bash
curl https://ingest.amlexia.com/healthSend a manual test (replace key):
bash
curl -X POST https://ingest.amlexia.com/v1/events \
-H "Content-Type: application/json" \
-d '{"sdk_key":"am_YOUR_KEY","events":[{"endpoint":"GET /health","method":"GET","status_code":200,"latency_ms":1}]}'401 Unauthorized
- Invalid or revoked SDK key.
- Key from a different project than the one you are viewing in the dashboard.
429 Too Many Requests
- Ingest rate limit exceeded for your key.
- SDKs retry automatically; if persistent, reduce event volume or contact support.
Events appear but wrong route names
- Dynamic segments not normalized — use framework middleware (Express, FastAPI, etc.).
- For manual
track(), pass normalized labels:GET /users/:id.
Next.js: no server events
- Instrument Route Handlers or server actions only — not Client Components.
- See Next.js SDK.
Python: events missing after deploy
- Ensure
shutdown()runs on worker exit (Gunicorn/Uvicorn lifecycle). - Use
AmlexiaClient.from_env()so env vars are read correctly.
Live stream empty but Overview has data
- Live uses SSE; check ad blockers and corporate proxies.
- Very low traffic may take a moment to show the next event.
High cardinality / noisy routes
- Avoid tracking static assets unless debugging.
- Normalize paths; do not use raw query strings as endpoint names.
Still stuck?
Email support@amlexia.com with:
- Project id (not the SDK key)
- Framework and SDK version
- Approximate time you sent test traffic
- Whether
curl /healthsucceeds