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

Struggling with RAG in PHP? Discover Neuron AI components

Implementing Retrieval-Augmented Generation (RAG) is often the first “wall” PHP developers hit when moving beyond simple chat scripts. While the concept of “giving an LLM access to your own data” is straightforward, the tasks required to make it work reliably in a PHP environment can be frustrating. You have to manage document parsing, vector embeddings,

Enabling Zero-UI Observability

It is getting harder to filter through the noise in our industry right now. New AI tools drop every day, and navigating the hype cycle can be exhausting. But the reality is that our day-to-day job as developers is changing. Most of us have already integrated AI agents (like Claude, Cursor, or Copilot) into our

Neuron AI Laravel SDK

For a long time, the conversation around “agentic AI” seemed to happen in a language that wasn’t ours. If you wanted to build autonomous agents, the industry nudge was often to step away from the PHP ecosystem and move toward Python. But for those of us who have built our careers, companies, and products on