Introduction
Structured logs from your apps, sent to a hosted service, with a dashboard to search them and play back what happened to someone.
Lyrelog records what happens inside your apps, one event at a time, and lets you read it back: search every event, follow one person through a session, see which errors reached the most people, chart how long a request takes on each version.
The lyrebird records every sound it hears and plays it back. Lyrelog does that for your app.
Quickstart
A project, its key and a first event in a few minutes.
SDKs
Swift, Android, React Native, Flutter, JavaScript, Python, Go and the JVM, or plain HTTP for anything else.
Dashboard
Search events, follow one person, see which errors reach the most people.
Command-line tool
Everything from the dashboard in a terminal, in JSON for scripts and agents.
What it is
- Logs about what happened to a person. A payment that was declined, a sync that
timed out, a screen someone left after two seconds. Each event has a stable name
(
payment_declined), a level, an area of the app and a few fields you can filter and chart by. - A hosted service. Your apps send events to
https://ingest.lyrelog.com, and you read them in the dashboard at app.lyrelog.com. You don't run anything. Your events are stored on Lyrelog's servers in Germany. Backups are kept for at most 30 days: on the same servers, and as an encrypted copy in Backblaze's EU data center in the Netherlands that Backblaze can't read. - SDKs that stay out of your code's path. Logging copies the event and returns; batching, gzip, retries and offline queues happen in the background. There are SDKs for Swift, Android, React Native, Flutter, JavaScript, Python, Go and Java and Kotlin servers, and a plain HTTP API for anything else. The SDKs aren't published yet: until they are, send events over the HTTP API.
- The dashboard, and a command-line tool. Read events in the browser, or from a terminal
with
lyrelog, which also writes JSON for scripts and coding agents.
Early access
Lyrelog is in early access, by invitation. Ask for one on lyrelog.com. When it's your turn, you get an email with a link that makes your account and your organization. See Getting access.
The Free plan covers 1,000,000 events a month. Paid plans aren't open yet. See Plans and usage.
What it isn't
Lyrelog is not product or marketing analytics. It has trends and funnels, but they are there to find flows that break (what share of submits fail, on which version), not to measure campaigns or conversion. Keep a tool like PostHog for that, and use Lyrelog for the question "what happened to this person, and why".
It is also not a crash symbolicator or a tracing system: crash reports arrive with frame offsets (symbolicate them with your dSYM), and there are no spans.
How the pieces fit
your app ──(SDK or HTTP, ingest key)──▶ ingest.lyrelog.com ──▶ your project's events
│
you ──(browser, signed in)──▶ app.lyrelog.com ◀───────────────────────┘Every project belongs to an organization. Its people see all its projects, and its plan covers them all.
Where to go next
Getting access
Ask for an invitation and make your account.
Quickstart
Create a project and send a first event with curl.
Events
Names, levels, areas, attributes and payloads.
HTTP API
Every field, limit and response of the ingest endpoint.
No events arrive
The usual reasons an event doesn't show up.
Pick your language
Apps
Web and servers
Anything else