Tempest
Code Execution Monitoring for Tempest applications
Last updated
Code Execution Monitoring for Tempest applications
PHP ^8.5
Tempest ^3.0
Install the latest version by:
composer require inspector-apm/inspector-tempestTempest will automatically discover the package provider and other library components.
You just need to put the Ingestion Key in your environment file:
INSPECTOR_INGESTION_KEY=[ingestion key]You can obtain an INSPECTOR_INGESTION_KEY creating a new project in your Inspector account.
Run the command below:
vendor/bin/tempest inspector:testGo to https://app.inspector.dev to explore your data.
You can connect the Inspector library documentation to your coding assistant as a Model Context Protocol (MCP) server.
It makes it easy for tools like Claude Code, Cursor, and VS Code extensions reliably understand what Inspector client library can do, its configurations, how to use it.
If you want to take full control over the Inspector client behaviour you need to install the inspector assets on your project directory.
The command below will add the app/inspector.config.php file providing the InspectorConfig instance:
It could be necessary to turn off monitoring based on url. Think about parts of your app that don't affect the user experience.
You can also use the wildcard character * to exclude all sub-paths.
You can ignore artisan commands by adding the command name to the ignoreCommands argument in the InspectorConfig configuration class:
Last updated
php tempest install inspector return new InspectorConfig(
...,
ignoreUrls: [
'/admin/*'
],
);return new InspectorConfig(
...,
ignoreCommands: [
'discovery:generate'
],
);