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

Agent Skills in PHP: On-Demand Skills for Neuron AI Agents

Every Neuron agent starts with a tidy instructions() method: a few lines describing who the agent is, what it should do, and how it should talk. Then the agent meets real users, and that method starts to grow. A customer needs reports in a specific format, so the format goes into the prompt. The support

Neuron 4 is Here 🚀 Welcome To The PHP Agentic Era

For the first year of this project, every conversation I had about Neuron AI started with the same question: Can PHP really do this, or are you a few years behind Python and pretending otherwise? At some point in the months after Neuron 3.x, I noticed the question had stopped coming. Not because I got

TypeSafe AI and Jev in PHP: Model Routing and Classifier with Neuron AI

Every agent I have written contains a line that took me ten seconds to type and that I kept second-guessing for months. That string decides the cost and the quality of every conversation the agent will ever have, and you choose it before seeing a single one. The same support agent will answer “Hi, where