Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Logs Bundle

Logs Bundle Laravel Package

norsys/logs-bundle

Symfony bundle by Norsys for centralized application logging. Integrates Monolog with configurable handlers, log channels, and formatting so teams can ship consistent, searchable logs across services with minimal setup.

View on GitHub
Deep Wiki
Context7

Bundle to manage logs in symfony application

Frequently asked questions about Logs Bundle
Is norsys/logs-bundle compatible with Laravel?
No. norsys/logs-bundle is a Symfony bundle designed for Symfony applications, not a Laravel package. Laravel has its own logging stack built on Monolog, so you should use Laravel's config/logging.php or a Laravel-specific logging package instead. You can still study its handler and channel approach when designing Laravel logging, but do not install it as a Laravel dependency.
How do I install norsys/logs-bundle with Composer?
Install it through Composer using composer require norsys/logs-bundle, then register the bundle in your Symfony application where bundles are enabled. The exact registration file depends on your Symfony version, so check the repository README for the current instructions. After installation, configure your Monolog handlers and channels in Symfony configuration.
What Symfony versions does norsys/logs-bundle support?
The provided context does not list supported Symfony or PHP versions, so verify the composer.json and README on GitHub before adopting it. Check the required symfony/monolog-bundle and PHP constraints to confirm compatibility with your application. If you are on an older or very new Symfony release, let Composer resolve dependencies and review any conflicts.
How do I configure Monolog handlers in norsys/logs-bundle?
The bundle integrates Monolog with configurable handlers, but the exact configuration keys are not included in the provided excerpt. In Symfony, Monolog handlers are typically defined under monolog.handlers, and the bundle may add its own conventions or presets. Start with a simple stream or rotating file handler, then consult the bundle documentation for any bundle-specific options.
Can I define custom log channels with norsys/logs-bundle?
The package description mentions log channels, which usually means you can separate application areas into distinct Monolog channels. In standard Symfony Monolog configuration, channels are declared under monolog.channels and assigned to handlers through the channels option. Verify the bundle README for whether norsys/logs-bundle adds any channel naming or routing conventions.
How does norsys/logs-bundle handle log formatting?
The blurb states that formatting is configurable, which likely means you can choose Monolog formatters or define custom formatter services. Symfony Monolog commonly supports line, JSON, and custom formatters, with JSON being useful for structured and searchable production logs. Check the bundle documentation for formatter-specific configuration and defaults.
Is norsys/logs-bundle suitable for production logging?
It can be suitable for production if you configure appropriate handlers, log rotation, retention, and monitored destinations. Avoid logging sensitive data, prefer structured formats such as JSON for searchability, and route errors to an alerting system. Test the configuration under realistic load to confirm it does not create excessive I/O or disk growth.
How do I test logging configuration with norsys/logs-bundle?
In Symfony, test logging by using a test environment configuration and a test or in-memory Monolog handler, then assert on the recorded log entries. For bundle-level behavior, write functional tests that boot the Symfony kernel and inspect the generated logs or handler output. Review the bundle's own test suite on GitHub for patterns you can reuse.
What are alternatives to norsys/logs-bundle for Laravel logging?
For Laravel applications, the primary alternative is Laravel's built-in logging system configured in config/logging.php, which supports single, daily, stack, Slack, and custom Monolog channels. You can also send logs to external aggregators or error-tracking services alongside Laravel's native channels. Use norsys/logs-bundle only as a conceptual reference, since it is built for Symfony.
Is norsys/logs-bundle actively maintained?
The provided context does not include maintenance metrics, so check the GitHub repository for recent commits, releases, issue activity, and supported dependency constraints. Review composer.json to confirm compatibility with your Symfony and PHP versions. Before using it in production, verify that the project is still receiving fixes or be prepared to maintain a fork.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console
pnscripts/filament-broadquill-lite
pnscripts/laravel-sentfold-lite
vleap/mx-sdk-laravel-internal
twidpay/utils
htetmyathlaing/scout-elasticsearch-driver
artisan-toolbox/front-awesome
ls/client-assistant
users-au/laravel-client
cgv/localized-resource
noith/settings
kda/laravel-package
kda/filament-dynamic-navigation
bypersoft/signbox
pairus/product-data
fayne/laravel-filament-cms-core