Skip to content

Commit a002b6e

Browse files
committed
formatting
1 parent 01aaa3b commit a002b6e

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

logging.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -60,16 +60,15 @@ Name | Description | Default
6060
`permission` | The log file's permissions | `644`
6161
`locking` | Attempt to lock the log file before writing to it | `false`
6262

63+
#### Configuring The Papertrail Channel
64+
65+
The `papertrail` channel requires the `url` and `port` configuration options. You can obtain these values from [Papertrail](https://help.papertrailapp.com/kb/configuration/configuring-centralized-logging-from-php-apps/#send-events-from-php-app).
66+
6367
#### Configuring The Slack Channel
6468

6569
The `slack` channel requires a `url` configuration option. This URL should match a URL for an [incoming webhook](https://slack.com/apps/A0F7XDUAZ-incoming-webhooks) that you have configured for your Slack team.
6670

6771
<a name="building-log-stacks"></a>
68-
69-
#### Configuring The PaperTrail Channel
70-
71-
The `papertrail` channel requires `url` and `port`. You can obtain these from [PaperTrail](https://help.papertrailapp.com/kb/configuration/configuring-centralized-logging-from-php-apps/#send-events-from-php-app) and can be defined in the .env file as `PAPERTRAIL_URL` & `PAPERTRAIL_PORT`.
72-
7372
### Building Log Stacks
7473

7574
As previously mentioned, the `stack` driver allows you to combine multiple channels into a single log channel. To illustrate how to use log stacks, let's take a look at an example configuration that you might see in a production application:

0 commit comments

Comments
 (0)