Skip to content

Commit b28bdc4

Browse files
committed
Merge pull request #4 from dimitrytarasov/patch-1
Fix Exec transport behavior description
2 parents f7e015b + cd611f6 commit b28bdc4

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ Install the latest version with `composer require stackify/logger`
1919
There are three different transport options that can be configured to send data to Stackify. Below will show how to implement the different transport options.
2020

2121
### ExecTransport
22-
ExecTransport does not require a Stackify agent to be installed because it sends data directly to Stackify services. It collects log entries in a single batch, calls curl using the ```exec``` function, and sends it to the background immediately [```exec('curl ... &')```]. This will affect the performance of your application minimally, but it requires permissions to call ```exec``` inside the PHP script and it may cause silent data loss in the event of any network issues. This transport method does not work on Windows. To configure ExecTransport you need to pass the environment name and API key (license key):
22+
ExecTransport does not require a Stackify agent to be installed because it sends data directly to Stackify services. It collects log entries in batches, calls curl using the ```exec``` function, and sends data to the background immediately [```exec('curl ... &')```]. This will affect the performance of your application minimally, but it requires permissions to call ```exec``` inside the PHP script and it may cause silent data loss in the event of any network issues. This transport method does not work on Windows. To configure ExecTransport you need to pass the environment name and API key (license key):
2323

2424
```php
2525
use Stackify\Log\Transport\ExecTransport;

0 commit comments

Comments
 (0)