Comment on page
Configuration
Customize the monitoring strategy in your Symfony application.
Here is the list of bundle options you can use to customize how Inspector collects data within your application.
Turn on/off monitoring in your application:
inspector:
ingestion_key: '%env(INSPECTOR_INGESTION_KEY)%'
# True by default
enabled: true
Turn on/off the unhandled exceptions reporting:
inspector:
ingestion_key: '%env(INSPECTOR_INGESTION_KEY)%'
# True by default
unhandled_exceptions: true
Turn on/off monitoring of database statements:
inspector:
ingestion_key: '%env(INSPECTOR_INGESTION_KEY)%'
# True by default
query: true
query_bindings: true
query_bindings
option allows you to collect the content of the parameters binded to a query.There may be parts of the application that you are not interested in monitoring. Maybe they were created for internal use, or for application maintainance, and have no impact on the user experience in production.
Inspector provides you several options to keep off the noise, and only monitor what metter.
You can turn off monitoring based on url. Paste the "ignore_urls" option below into the
config/packages/inspector.yaml
file to add your custom entries:inspector:
ingestion_key: '%env(INSPECTOR_INGESTION_KEY)%'
ignore_urls:
- '_wdt'
- '_profiler'
- '_profiler_home'
- '_profiler_search'
- '_profiler_search_bar'
- '_profiler_phpinfo'
- '_profiler_search_results'
- '_profiler_open_file'
- '_profiler_router'
- '_profiler_exception'
- '_profiler_exception_css'
As you can see above, we exclude several http endpoints by default. You can continue adding yours as needed.
You can ignore commands adding the command defaultName to the
ignore_commands
collection in the config/packages/inspector.yaml
file.inspector:
ingestion_key: '%env(INSPECTOR_INGESTION_KEY)%'
ignore_commands:
- 'app:create-user'
Last modified 2yr ago