Managed Berserk
First steps on a Berserk deployment we run for you
We run your deployment at https://<your-domain>. Your welcome message has an invite link and an ingest token.
Create your user
Open the invite link and choose a password. The link works once and expires after 7 days; ask us for a new one if yours has.
You sign in as an admin. Invite your team from Settings → Members (invites).
Find your tables
Your default database comes with two tables:
| Table | Receives |
|---|---|
logs | logs and traces |
metrics | metrics |
Query them on the Query page or with the CLI, starting with logs | take 10. Traces go to logs too, so trace-find finds each span's logs in the same table.
No tables yet? Create them and an ingest token yourself: Tables.
Send your telemetry
Send OTLP over gRPC to ingest.<your-domain>:4317 with your ingest token. For an OpenTelemetry Collector:
exporters:
otlp_grpc/berserk:
endpoint: "ingest.<your-domain>:4317"
headers:
authorization: "Bearer <your-ingest-token>"Add otlp_grpc/berserk to your logs, metrics and traces pipelines; the token routes each signal to its table. For production, start from the recommended collector configuration. Other shippers: Ingestion.
The endpoint takes OTLP over gRPC with TLS only; OTLP/HTTP is not served.
Connect your AI agent
Add Berserk's MCP server to Claude Code (2.1.232 or later), then run /mcp in Claude Code to sign in through the browser:
claude mcp add --transport http berserk https://<your-domain>/mcpOther MCP hosts and token-based setups: MCP. To have your agent run bzrk instead: AI Agent Setup.