Introduction

quiet-guard/monitor-symfony-bundle brings Quiet Guard to Symfony applications. It is a thin Symfony bundle on top of the framework-agnostic core quiet-guard/monitor-php: the core does the actual work, building payloads, scrubbing sensitive data and talking to the server over a dependency-free curl transport, while the bundle wires it into Symfony's service container and kernel events so it feels native to a Symfony project.

What it does

Once installed and configured, the bundle:

• captures unhandled exceptions through an event subscriber on the kernel.exception event and forwards them to your Quiet Guard server;
• forwards application logs through an optional Monolog handler that batches records and ships them to the server;
• exposes a shared Reporter service you can inject to report exceptions or send logs by hand.

Everything is additive and non-blocking: reporting never alters the HTTP response, never changes exception propagation, and never throws, monitoring must not break the host application.

How it fits together

The bundle registers a small set of services in the container, all built from the monitor-php core types: a Config value object, a Scrubber, an ExceptionPayloadBuilder, a curl HttpClient and the Reporter that ties them together. You only declare a monitor config tree; the bundle constructs and connects these for you. There is no XML/YAML service resource, the wiring lives in the bundle's dependency-injection extension.

Because it shares the same ingestion API and the same core as the Laravel SDK, a Symfony app appears in the same dashboard as your Laravel apps, one cockpit for a mixed PHP fleet.

Requirements

Next steps

• Installation: require the package and register the bundle.
• Configuration: the full monitor config tree, key by key.
• Usage: what is captured automatically and how to report manually.
• Upgrading: versioning and compatibility.