Frequently asked questions

BunnyLogs is a real-time log streaming platform for developers. You send log entries to a logspace via HTTP POST, email, Slack, Telegram, WhatsApp, Discord, or OpenTelemetry — and they appear instantly in your browser over WebSocket. No agent to install, no SDK required.

Click New stream on the dashboard (or visit /live/). You get a UUID-based URL like /live/<uuid>. POST log entries to that URL from anywhere — curl, Python, a CI pipeline, or a chat message.

No. The only requirement is the ability to make an HTTP POST request. A UUID in the URL is all the authentication you need. Optional SDKs exist for Python (pip install bunnylogs) and Flutter, but they are convenience wrappers around the same HTTP API.

POST JSON to https://bunnylogs.com/live/<uuid> with Content-Type: application/json:

curl -X POST https://bunnylogs.com/live/<uuid> \
  -H 'Content-Type: application/json' \
  -d '{"message":"deploy started","level":"INFO","program":"ci"}'

• message (required) — the log text. Only this field counts toward billing.
• level — severity string, e.g. DEBUG, INFO, WARNING, ERROR.
• program — the source service or component name.
• timestamp — ISO 8601 datetime; defaults to server receive time if omitted.

Yes. POST a JSON array of log entry objects and all entries are ingested in one request:

[
  {"message": "step 1 done", "level": "INFO"},
  {"message": "step 2 done", "level": "INFO"}
]

No. Possession of the UUID grants write access to that logspace. Keep your UUID private if you want to restrict who can post to it.

No artificial rate limits. The system is designed for burst traffic from deployments, CI pipelines, and live services.

Your browser connects to the logspace over WebSocket. When a new log entry is POSTed, the server broadcasts it through Redis to all connected viewers — typically appearing sub-100 ms after ingestion.

Yes. The live viewer has a filter bar where you can narrow by level (DEBUG, INFO, WARNING, ERROR), program name, or free text in the message. Filters apply in real time without a page reload.

Share the /live/<uuid> URL — anyone with it can watch the stream, no account required. For access control, use the team sharing feature in settings to invite members with view-only or post permissions, so access can be revoked at any time.

Ingest sources: HTTP POST, email (SMTP), Slack, Telegram, WhatsApp, Discord, Facebook Messenger, OpenTelemetry OTLP, IFTTT, Pipedream, TradingView webhooks, Bybit, Thalex, GitHub Actions, Bitbucket Pipelines, Fly.io, and any HTTP client.

Alert delivery: Webhook, Slack, Telegram, Discord, email, Messenger, Pipedream.

Language SDKs: Python, Flutter, PHP, Node.js, Go, Ruby, Bash, iOS (oslog & CocoaLumberjack), Android.

Send an email to <your-username>@bunnylogs.com. The body of the email is parsed and each line becomes a separate log entry in your email logspace. The subject line is ignored. You can send from any email client or automated system.

Yes. BunnyLogs exposes an OpenTelemetry OTLP HTTP endpoint at /otlp/<uuid>/v1/logs. Configure your OTel SDK or collector to export logs there — no authentication header required, just the UUID in the path. See the OpenTelemetry guide for setup details.

Yes. Every log line that enters a logspace, regardless of its source, counts toward your monthly ingest total.

An alert is a rule that watches a logspace for matching entries. When a log entry matches all conditions, BunnyLogs delivers a notification to one or more alert channels. Conditions use AND logic and can match on level, program name, or message text.

• Level — exact match, e.g. ERROR
• Program — exact match on the program/service name
• Message — substring match on the message text

All specified conditions must match for the alert to fire.

Webhook (any HTTP endpoint), Slack channel, Telegram chat, Discord channel, email address, Facebook Messenger, and Pipedream. You can attach multiple delivery channels to a single alert rule.

Open the alert in the alert editor and click Send test. BunnyLogs immediately fires a test notification to all configured channels so you can confirm delivery without waiting for a real log match.

No. You can create as many alert rules as you need across all plans, including the free tier.

30 days. Log entries are indexed in Elasticsearch and automatically purged after 30 days. Real-time streaming is unaffected — there is no retention limit on the live view.

Yes. The history view at /live/<uuid>/history lets you full-text search all indexed log entries within the 30-day window. Filter by level, program, and message text, or jump directly to a specific timestamp.

Free up to 100 KB ingested per month. After that, €5 per started GB — billing rounds up to the next full GB. No seats, tiers, or per-integration charges. See the pricing page for a full breakdown and cost calculator.

The byte size of the message field in each log entry. Metadata fields (level, program, timestamp) are not counted. Billing rounds up to the next full GB — 1.1 GB costs the same as 2 GB (€10).

Per account. All your logspaces share a combined 100 KB monthly free allowance.

You can configure a maximum monthly ingest limit (in MB or GB) on any logspace. Once that limit is reached, further POST requests to that logspace return 429 Too Many Requests until the month resets. Your bill cannot exceed the cap you set.

Yes. Open the logspace settings and use the Invite member form to send an email invitation. You choose whether each member can view logs, post logs, or both.

• View — can watch the live stream and search history.
• Post — can send log entries to the logspace.

Both permissions are independent and set per member. You can update or revoke access at any time from the logspace settings.

Yes. Go to Settings → Shared with me and click Leave next to the logspace you want to remove yourself from.

All infrastructure runs in the European Union. Your log data never leaves EU jurisdiction, making GDPR compliance straightforward for you and your users.

Yes. All data is stored on EU-based servers with no cross-border transfers. You control what data you send — avoid including PII in log messages if you don't have a legal basis for storing it. See our Privacy Policy.

Anyone who has the logspace UUID can view the live stream and history. For team logspaces, only explicitly invited members can access logs via their account. BunnyLogs staff can access data only for operational and support purposes.

By UUID possession for anonymous access, and by account membership for invited team members. You can revoke member access at any time from the logspace settings. Treat the UUID like a secret — anyone who has it can read and write logs.

Yes. Go to your profile page and click Delete account. This permanently deletes your account and all data associated with it, including all logspaces you own.

Yes. BunnyLogs supports sign-in via Google and GitHub in addition to email/password. Choose your preferred method on the sign-in page.