Download the PHP package zanbug/symfony without Composer
On this page you can find all versions of the php package zanbug/symfony. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download zanbug/symfony
More information about zanbug/symfony
Files in zanbug/symfony
Package symfony
Short Description Zanbug error & monitoring SDK — Symfony bundle that auto-captures exceptions.
License MIT
Homepage https://zanbug.com
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package symfony
zanbug/symfony
Symfony bundle for the Zanbug error & monitoring SDK.
It auto-captures unhandled exceptions via a kernel.exception listener and
initializes the framework-agnostic zanbug/php-sdk core for you.
Compatible with Symfony 3.4 → 7.x and PHP 7.1+.
Install
Enable the bundle
Add it to config/bundles.php (Symfony Flex / 4+):
On Symfony 3.4 (AppKernel), add it to registerBundles():
Configure
Create config/packages/zanbug.yaml:
Then set your API key (e.g. in .env):
That's it — unhandled exceptions are now reported to Zanbug automatically.
Manual capture
You can also report manually anywhere in your app:
Configuration reference
| Key | Type | Default |
|---|---|---|
api_key |
string | '' |
host |
string | https://zanbug.com |
environment |
string | production |
release |
string | null |
enabled |
bool | true |
capture_requests |
bool | false |
capture_queries |
bool | true |
slow_query_ms |
int | 1000 |
sample_rate |
float | 1.0 |
Slow query monitoring
Doctrine's SQLLogger interface was removed in DBAL 4, so the bundle does not hook Doctrine automatically. Pick whichever fits your setup (queries faster than slow_query_ms are always dropped by the SDK):
-
Doctrine DBAL 2.x / 3.x — register the bundled logger yourself (e.g. on
kernel.requestor in a decorator): -
Any DBAL version / no Doctrine — record manually where you run queries:
- Plain PDO — use the drop-in
\Zanbug\Sdk\Support\TracedPdofrom the core SDK.
Updating the SDK
Automatic: ZANBUG_AUTO_UPDATE=true (or 'auto_update' => true in the SDK config) — once a day at the end of a CLI run the SDK updates itself in a detached process (log <tmp>/zanbug-update.log). Restart workers afterwards. Details: zanbug/php-sdk README.
Log capture (errors logged but not thrown)
Errors you catch and log — but never re-throw — only hit the log file. Enable
capture_logs in the SDK init and forward them to Zanbug with recordLog():
Monolog users can register a tiny handler whose write() calls
Zanbug::recordLog($record['level_name'] ?? $record->level->getName(), $record['message'] ?? $record->message, $record['context'] ?? $record->context)
(works for Monolog 2 arrays and Monolog 3 LogRecord). Records below log_level
are dropped; context is redacted; recordLog() never throws.
All versions of symfony with dependencies
zanbug/php-sdk Version ^2.0.0
symfony/http-kernel Version >=3.4
symfony/dependency-injection Version >=3.4
symfony/config Version >=3.4
symfony/event-dispatcher Version >=3.4