- Does apirelio/symfony work with Laravel?
- No. It is a Symfony bundle for Symfony 6.4–8 APIs, not a Laravel package, so it does not provide a Laravel service provider or Laravel middleware. Laravel teams evaluating it should treat it as a Symfony-only integration and look for a Laravel-specific monitoring option instead.
- What does Apirelio Symfony actually monitor?
- It records normalized endpoint errors, latency and release metrics, and ties failures to the affected customers. The bundle does not capture request or response bodies, credentials, cookies, query strings, IP addresses or personal data. Delivery is described as fail-safe.
- How do I install and configure apirelio/symfony?
- Install it with Composer, register Apirelio\Symfony\ApirelioBundle in config/bundles.php, and set the APIRELIO_* environment values such as API key, endpoint, service, environment and release. One project key from the Apirelio dashboard configures the integration, with YAML config under config/packages/apirelio.yaml. The README excerpt shows composer require apirelio/symfony:^0.2 while the assessment references a v1.0.0 stable line, so confirm the current constraint on Packagist before pinning.
- Which Symfony and PHP versions are supported?
- The README lists Symfony 6.4, 7.4 and 8.x, with PHP 8.2, 8.3 or 8.4; Symfony 8 itself requires PHP 8.4. The assessment notes that v1.0.0 release notes declare PHP 8.2–8.5 support, so PHP 8.5 should be verified in the package CI rather than assumed. Match these constraints against your application runtime before adopting.
- Does it capture request or response payloads or personal data?
- No. The bundle is designed to record normalized endpoint metrics and customer context without capturing request or response bodies, credentials, cookies, query strings, IP addresses or personal data. Shared privacy rules and delivery primitives come from apirelio/php-core, which Composer installs automatically.
- What dependencies does apirelio/symfony bring in?
- It is installed via Composer and pulls in apirelio/php-core for the shared event contract, privacy rules and delivery primitives. You should still check Composer constraints against your Symfony, PHP, database, cache, queue and filesystem setup. Use composer why-not to confirm there are no dependency conflicts before rollout.
- Is apirelio/symfony production-ready and stable?
- The assessment describes a v1.0.0 release with a stable 1.x semver commitment, which is a positive stability signal. However, release notes are sparse and the README excerpt shows a ^0.2 install command, so this is a provisional initial assessment. Pin a known version, validate in staging and keep a rollback option before production use.
- How does fail-safe delivery work if Apirelio is unavailable?
- The README states that delivery is fail-safe and that no request or response payloads are captured. It does not document the exact outage behavior in the provided excerpt, so do not assume it cannot affect request handling until you test it. Simulate an unreachable endpoint or invalid project key in staging and confirm your API behavior and logs remain acceptable.
- What should I test before adopting it in a Symfony API?
- Install it in a sandbox, register the bundle, verify config caching and environment variables, then generate representative errors and latency to confirm customer attribution and release tagging. Test the disabled mode, an unavailable Apirelio endpoint and your normal application test suite. Check logs for bundle boot or delivery failures before promoting to staging and production.
- Are there alternatives for Laravel teams wanting customer-level API monitoring?
- Laravel teams should evaluate Laravel-aware APM or error-tracking tools and custom middleware/events rather than installing a Symfony bundle. Apirelio Symfony is relevant only if you run Symfony APIs and want customer-level attribution without payload capture. Compare alternatives on privacy behavior, release tracking, customer mapping, maintenance cadence and production outage handling.