Laravel and Symfony console command monitoring

Valerio Barbera

Recently the support for wildcard was introduced in the Symfony library to help developers turn-off monitoring in some parts of their applications using URL path.

/api/users*

It was already supported in the Laravel package.

I received a lot of feedback from our users to make it possible also for commands. And it’s what this library update is about.

For more technical articles you can follow me on Linkedin or X.

Laravel/Symfony console command monitoring

Typically the console commands in the Laravel and Symfony frameworks are organized by namespace like:

make:migration
make:middleware
make:model

Before this release you have to manually add all the commands you want to exclude from your monitoring metrics in the inspector configuration file.

'ignore_commands' => [
    'make:migration',
    'make:middleware',
    'make:model',
],

Ignore Console Commands With Wildcard

Now instead of forcing you to list all commands you want to ignore one by one we introduced the support for the wildcard character “*” to make this configuration a lot easier and the inspector configuration file shorter.

You can change the configuration above with a single line in the inspector configuration file:

'ignore_commands' => [
    'make*',
],

In the same way you did URLs:

'ignore_urls' => [
    'api/users*',
],

For more technical articles you can follow me on Linkedin or X.

Monitor your Symfony application for free

Inspector is a Code Execution Monitoring tool specifically designed for software developers. You don’t need to install anything on the infrastructure, just install the Symfony package and you are ready to go.

If you are looking for HTTP monitoring, database query insights, and the ability to forward alerts and notifications into your preferred messaging environment try Inspector for free. Register your account.

Or learn more on the website: https://inspector.dev

Related Posts

Parallel Branches in Neuron AI Workflow

One of the things I didn’t expect when I started building Neuron AI was how much the design of the framework would be shaped by the people using it. I started this project to solve my own problems: I wanted PHP developers to have a clean, idiomatic way to integrate AI into their applications without

How to Stop a Streamed AI Response Mid-Flight in Neuron AI v3

One thing I didn’t anticipate when building Neuron AI was how many edge cases would surface not from the AI integration itself, but from the UI layer sitting on top of it. Developers don’t just want agents that work. They want agents that feel right to use. And the moment you start building chat interfaces