You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: telescope.md
+6-4Lines changed: 6 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ Telescope exposes a dashboard at `/telescope`. By default, you will only be able
108
108
<aname="filtering-entries"></a>
109
109
### Entries
110
110
111
-
Telescope allows you to record filtered entries by registering a callback via the `filter`method in your `app/Providers/TelescopeServiceProvider.php` file:
111
+
You may filter the data that is recorded by Telescope via the `filter`callback that is registered in your `TelescopeServiceProvider`. By default, this callback records all data in the `local` environment and exceptions, failed jobs, scheduled tasks, and data with monitored tags in all other environments:
112
112
113
113
/**
114
114
* Register any application services.
@@ -134,7 +134,9 @@ Telescope allows you to record filtered entries by registering a callback via th
134
134
<aname="filtering-batches"></a>
135
135
### Batches
136
136
137
-
Besides filtering at the entry level, you may also filter batches (request or console application cycles) while retaining all the entries associated with the filtered batches by using the `filterBatch` method:
137
+
While the `filter` callback filters data for individual entries, you may use the `filterBatch` method to register a callback that filters all data for a given request or console command. If the callback returns `true`, all of the entries are recorded by Telescope:
138
+
139
+
use Illuminate\Support\Collection;
138
140
139
141
/**
140
142
* Register any application services.
@@ -145,7 +147,7 @@ Besides filtering at the entry level, you may also filter batches (request or co
0 commit comments