Events
lyrelog events searches with the explorer's filters, follows new events live, and shows one event in full.
lyrelog events is the explorer in a terminal. It lists a
project's events, newest first, from the last 24 hours unless you say otherwise. It also
answers to lyrelog logs and lyrelog log.
lyrelog events --level warning+ --since 7dTilefall · production · last 7 days
10:30:07 ▌error cloud_save_failed sync reason=schema_mismatch record=progress status=422
10:27:43 ▌error cloud_save_failed sync reason=schema_mismatch record=progress status=422
10:24:48 ▌error cloud_save_failed sync reason=schema_mismatch record=progress status=422
10:22:05 ▌error cloud_save_failed sync reason=schema_mismatch record=progress status=422
10:17:06 ▌error chat_socket_gave_up chat attempts=4 match_id=0d9acb1f-503f-4818-a5a1-19336d1f0d8a
Showing 5 events. For more: --cursor MTc5NTE2NjIyNjExMTo3...The first line names the project, the environment and the time window. Each event is one line: its time, its level, its name (message), its area (category) and its attributes. Events from other days show the date too.
Filters
The filters are the explorer's, and they take what its address takes: "a|b" for any of
several values, "!a" for anything but that one. Quote them, because | and ! mean
something to the shell.
| Flag | Filters by |
|---|---|
--level | Levels: error, error,critical, or warning+ for warning and worse. Levels are trace, debug, info, notice, warning, error, critical. |
--message | The event name (message), exactly |
-q, --query | Search the message, area and attributes |
--category | Area (category): checkout, "a|b" or "!a" |
--attr | An attribute, path:value, or path!:value for not. Repeat it for more. |
--user | One person's id (the user_id the app sends) |
--session | One session's id |
--install | One install's id |
--version | App version: 2.4.0, or "2.4.0|2.4.1" |
--platform | Platform: ios, android, web, python... |
--device | Device model |
--os | OS version |
--country | Country code: ES, or "ES|PT" |
--locale | Locale: es_ES |
--verified | How the sender was proven: server, app_attest, none. "!none" keeps only verified events. |
--env | Environment. The default is the project's default, as in the dashboard; all searches every one. |
lyrelog events --attr board.size:9 --attr result!:win
lyrelog events --level error --version "2.4.0|2.4.1" --platform '!web'
lyrelog events --user pl-fe0958c6 --since 7d --limit 500
lyrelog events --verified '!none'
lyrelog events --env all -q "card declined"The default environment is the project's, so events sent under development don't appear
unless you pass --env development or --env all (see
Environments).
Time
| Flag | What |
|---|---|
--since | A window ending now: 15m, 1h, 6h, 24h, 7d, 30d, or any number of s, m, h, d or w. Default 24h. |
--from | The start |
--to | The end. Default now. |
--oldest-first | Oldest first, from the start of the window |
--from and --to take:
- RFC 3339:
2026-11-19T10:00:00Z - a date and time in your computer's time zone:
2026-11-19 10:00 - a date:
2026-11-19, which means midnight at its start, in your time zone - Unix milliseconds (
1763550000000) or seconds - how long ago:
2h,3d
--since can't go with --from or --to. With only --from, the window ends now; with only
--to, it starts 24 hours before.
lyrelog events --from 3d --to 2d
lyrelog events --from 2026-11-15 --to 2026-11-16 --oldest-firstTilefall · production · Nov 15 00:00 to Nov 16 00:00
Nov 15 00:00:00 ▌info leaderboard_submit_confirmed leaderboards board=tilefall.daily.pure latency_ms=420
Nov 15 00:00:11 ▌info game_started game board.seed=4052403362615 board.size=7 m…
Nov 15 00:00:17 ▌info match_round_won multiplayer match_id=b60cc0cc-b294-46a3-9186-35c71a…How many, and the rest
| Flag | What |
|---|---|
-n, --limit | How many events at most. Default 100. Pages of up to 1,000 are fetched as needed. |
--cursor | Carry on from where a previous list stopped |
When there are more events than --limit, the last line gives the --cursor to pass for the
next ones. Run the same command again with that flag added, keeping the same filters. In JSON
mode, the cursor goes to stderr as {"more":true,"next":"--cursor ..."} (see
The JSON contract).
Follow new events
-f (--follow) prints the latest events from the last hour (up to --limit, oldest first),
then each new one as it arrives, until you press Ctrl-C. It asks every 4 seconds, as the
dashboard's live mode does, for what Lyrelog received since the last time. New events are
printed in the order they arrived, so a batch a phone sends late, after being offline, shows
when it arrives, with its own (older) times, as long as those are within the last 2 days.
lyrelog events -fTilefall · production · following, Ctrl-C to stop
10:41:52 ▌info app_launch app cold_start_ms=612 launch_reason=iconlyrelog events -f --level error follows only errors.
The filters work as usual. --since, --from and --to don't, because it shows what
arrives from now on. In JSON mode it writes one JSON object a line (NDJSON); each has
received_at, when Lyrelog received it (Unix ms), next to its own ts. If the server
can't be reached for a while, it says so on stderr and keeps trying. It stops if the session
ends or the project is gone.
events get
One event in full: who, where, the app, the device, its attributes and its payload.
lyrelog events get adea33e4-26eb-422e-b904-96649c0e7830▌ cloud_save_failed error
sync
Time 2026-11-20 10:30:07.485 CET 8m ago
Event adea33e4-26eb-422e-b904-96649c0e7830
Player pl-fe0958c6
Session 51e19a18-ca3e-4428-a10b-baeadc7eaaf8
Install 76f5a7d0-81b0-4c36-8908-eefd6c936abf
App com.example.tilefall 1.6.3 (202609301304)
Device iPhone18,2 iOS 27.2.0
Locale fr_FR
Country FR
Environment production
Platform ios
Attributes
{
"reason": "schema_mismatch",
"record": "progress",
"status": 422
}
Payload
{
"description": "The server refused the save",
"detail": "field 'mode' is not allowed in format 3; expected format 4"
}The tool finds the event by its id among everything the project keeps (its whole retention).
Pass --ts with the event's time in Unix milliseconds (the ts field of the JSON) to go
straight to it, skipping that lookup.
| Flag | What |
|---|---|
--ts | The event's time in Unix milliseconds (skips the lookup) |
events summary
The totals (events, people, sessions, errors) and the most frequent values of each field, as
the explorer's side panel shows them. It takes the same filters and time flags as events.
lyrelog events summary --since 7dTilefall · production · last 7 days
52,886 events 300 players 3,202 sessions 1,127 errors
category game 11.6k leaderboards 10k app 7,110 daily 5,362 campaign 5,126 account 3,304
level info 36.7k debug 13.7k error 1,110 warning 1,074 notice 292 critical 17
version 2.0 30.4k 1.6.3 22.5k
...events values
The most frequent values of one field, or of an attribute (attr.<path>), within the
filters: what the explorer's filter menu offers. Fields include level, category,
message, version, device, country, environment, platform and verified.
lyrelog events values message --level error --since 7dTilefall · production · last 7 days
Message Events Players
cloud_save_failed 823 124
daily_upload_failed 178 124
match_update_denied 43 38
leaderboard_submit_failed 29 17
chat_socket_gave_up 28 28
purchase_failed 9 8lyrelog events values attr.board.size| Flag | What |
|---|---|
--search | Only values containing this |
It also takes the filters and time flags of events.
events attributes
The attribute paths events carry, most common first. Also lyrelog events attrs.
lyrelog events attributes --of game_won --numericAttribute Events
hints_used 360
seconds 360| Flag | What |
|---|---|
--of | Only in these events (messages): "a|b" |
--numeric | Only attributes with numbers, the ones insights trend --metric value can chart |
It also takes the filters and time flags of events.