- Can I use this Symfony bundle directly in a Laravel project without Symfony dependencies?
- No, the bundle requires Symfony components like `symfony/event-dispatcher`. For Laravel, isolate it in a separate service (e.g., Docker container) or create a facade layer to translate Laravel’s `ExceptionOccurred` events to Symfony’s `KernelEvents`. This avoids polluting your Laravel monolith.
- How do I forward Laravel’s Monolog logs to AppLogger without the full Symfony bundle?
- Use Laravel’s Monolog handlers to send logs directly to AppLogger’s API via HTTP. This bypasses Symfony dependencies but limits features like exception grouping. Configure a custom handler in `config/logging.php` to target AppLogger’s endpoint with your API key.
- Does AppLogger support Laravel’s structured logging (arrays, context data) natively?
- The bundle expects Monolog records, which Laravel’s Log facade already uses. Structured data (e.g., `['user_id' => 123]`) will forward as-is, but verify AppLogger’s schema compatibility. For complex arrays, normalize them to JSON strings or flatten keys to avoid parsing issues.
- What happens if AppLogger’s API is unreachable? Will errors be lost?
- The bundle uses Symfony’s async HTTP client, which buffers logs locally and retries on failure. For Laravel, replicate this with a queue job (e.g., `LogToAppLoggerJob`) that handles dead-letter queues for persistent failures. No data is lost if your queue system persists messages.
- How do I correlate frontend errors (JS SDK) with backend Laravel errors in AppLogger?
- Include a `session_id` or `request_id` in both frontend and backend logs. The JS SDK auto-injects session IDs; ensure Laravel’s Monolog adds the same ID via a stack context or middleware. AppLogger’s UI will group errors by these IDs for unified debugging.
- Which Laravel versions are supported, and are there Symfony version conflicts?
- The bundle targets PHP 8.1+ and Symfony 6.3+, but Laravel compatibility depends on your setup. If using the facade pattern, test with Laravel 9/10. Symfony dependencies (e.g., `symfony/console`) may conflict; isolate them in a separate service or use a container like Docker to avoid version clashes.
- Is there a performance impact from async logging in high-traffic Laravel APIs?
- Minimal, as the bundle uses non-blocking HTTP calls. Monitor queue backlog or async client buffers under load. For APIs with >10K RPS, consider batching logs further (e.g., every 500ms) or using a dedicated logging microservice to offload AppLogger traffic.
- How do I migrate from Sentry/Rollbar to AppLogger in Laravel?
- Replace Sentry’s `ExceptionHandler` with a custom Laravel handler that dispatches events to the AppLogger facade. For Rollbar, swap its Monolog handler with AppLogger’s. Test in staging first, as error grouping and UI may differ. Use AppLogger’s API key in `config/app.php` or environment variables.
- Can I use this bundle for APM (e.g., request tracing, metrics) beyond error tracking?
- No, AppLogger focuses on error tracking and log aggregation. For APM, pair it with Laravel Telescope or Blackfire. The bundle’s async design is ideal for logs, but lacks features like distributed tracing or latency metrics. Use a dedicated APM tool for those needs.
- What’s the maintenance status of this bundle, and is AppLogger’s platform reliable?
- The bundle was last updated in 2026, suggesting active development. AppLogger’s EU hosting and GDPR compliance are strong selling points, but evaluate their SLA and uptime metrics. Check their status page and community forums for outage history before committing to a migration.