Getting started
Keep track of (all) the requests a connector executes.
Log those requests/responses to your database, keep the logs in-memory or bring your own storage implementation.
Configuration
.env configuration:
# Should any requests be logged? if not defined, defaults to true
SALOON_REQUEST_LOGS=false# If not set, the default database connection will be used
SALOON_REQUEST_DB_CONNECTION=
# If not defined, defaults to 14 (how many days should requests be stored in the db)
SALOON_REQUEST_PRUNE=14In the saloon-utils.php config file you can also define which requests or connectors will be ignored.
Any requests or connectors defined under saloon-utils.logs.ignore will never be logged, checks defined on the request- or connector-level will be bypassed.
Setup
Ensure your connector uses the LoggerPlugin trait.
Without any other configuration all requests this connector executes will be stored with the database logger.
Pools & concurrency
Our LoggerPlugin plugin uses Saloon's middleware to track requests, however, when pooling requests, the response middlewares are not executed.
You can still pool requests with this plugin and have logging applied by creating a logged pool:
The LoggerPool can be considered identical to Saloon's Pool class.
Last updated