Logs · Guides
Search your logs
Find lines by text, level, channel, time or request, one environment at a time, newest first.
Open Search in your project's Logs. It shows the last 24 hours of one environment, newest first, until you narrow it.
Choose the environment
The switch above the search picks the environment: the project's production one first, as the project's list at id orders them. Only environments that have sent lines are in it. A name your app sent that isn't one of the project's environments is there too, after the others, so its lines can still be found.
Search by text
Type in Text and press Search. It finds lines whose message, context or extra contains what you typed, up to 200 characters. There is no special syntax: payment failed finds those two words together, as written.
Narrow by level, channel and more
The fields under the text narrow the lines further. A choice in a list applies at once. Each filter in use shows as a chip above the results, which takes itself off when you click it.
| Filter | What it keeps |
|---|---|
| Level | That level or worse: “Warning or worse” keeps warnings, errors and the levels above. The levels, mildest first: debug, info, notice, warning, error, critical, alert, emergency. |
| Channel | Lines of one channel. Lines of the default channel are app; a channel of its own name, such as payments, is listed under its name (see Channels and levels). |
| Host | Lines from one server. |
| Release | Lines from one build, the latest first in the list. |
| Transaction | What was running, without values: GET /invoices/{invoice}, job App\Jobs\SendInvoice, artisan invoices:remind. |
| Request id | Every line of one request. See Read one request's lines. |
The lists offer what the environment has sent. In the results, a line's channel, transaction and host are links that narrow the search to theirs, and its request opens every line of that request.
Choose the time
The quick times are 15 minutes, 1 hour, 6 hours, 24 hours, 7 days and Everything kept. The search starts with 24 hours, and with everything kept when it looks for a request id.
For an exact stretch, open An exact time and fill in From, To or both. They are read in the time zone shown beside them, the one in your preferences, and they win over the quick times.
Read the results
- Lines over time: bars of the lines in the time you chose, by level. Each bar is a link to its own stretch.
- The totals: how many lines, how many warnings or worse and how many errors or worse. Click a total to keep only those.
- Lines: newest first, 100 a page, with Older and Newer to page on. The heading says how many days the environment keeps its lines.
Open a line
Click a line's time to open its page. It shows:
- its level, time and message,
- its environment, channel, transaction, host, release and request; “only this” beside the channel, transaction, host and release narrows the search to it,
- when it arrived, and how long it waited in your server's spool when that was a minute or more,
- its context and extra as trees, and as JSON to copy,
- the lines its server wrote right before and after it.
Around this line searches every line of its environment from 5 minutes before it to 5 minutes after. The request id opens every line of its request.
Share a search
Everything a search holds is in its address, so a link opens the same lines for anyone on the project. Copy link copies it, page included; a line's page has its own. Watch these live opens the live view with the same filters.
When nothing matches
- No line matches. Choose a longer time or take a filter off. A level filter keeps that level and worse only.
- The line is too old. Lines older than their environment keeps them are deleted every hour. A search around a line that is gone shows the last 24 hours instead. See Choose how long lines are kept.
- The time looks off. Times are shown and read in the time zone in your preferences, not the server's.
- No lines at all. The app hasn't sent any to this environment yet. See Nothing arrives.