- Do I install apirelio/php-core directly or is it pulled in by a Laravel package?
- For Laravel applications, install the apirelio/laravel adapter; Composer pulls apirelio/php-core in transitively. The core is framework-independent and is documented as the shared building block behind the official Apirelio PHP SDKs. Install apirelio/php-core directly only if you are building a custom adapter or integrating outside the official framework packages.
- Is there a Laravel adapter for Apirelio, or do I have to wire it myself?
- The README names apirelio/laravel as the framework adapter that applications normally install, alongside apirelio/symfony and apirelio/nette. Those adapters are responsible for adapting requests, routes, dependency injection and native queue systems. The core package handles the stable event contract, privacy rules, error-code extraction, retry orchestration and buffered delivery.
- What PHP and Laravel versions does apirelio/php-core support?
- The package requires PHP 8.2, 8.3 or 8.4 according to its README. Because Laravel 11 and 12 both require PHP 8.2 or newer, the core fits those Laravel versions when used through the Laravel adapter. Laravel 10 and earlier are excluded by the PHP 8.2 floor, so plan an upgrade before adopting it on older applications.
- Does Apirelio capture request and response payloads or customer PII?
- The package is positioned as privacy-safe, and the README explicitly states that no request or response payloads are captured. It owns a stable event contract plus metadata privacy rules and error-code extraction, so adapters can send customer-aware monitoring events without shipping raw bodies. You should still review your adapter configuration and the Apirelio docs to confirm exactly which metadata fields are allowed in your environment.
- What happens if the Apirelio API is unreachable and will monitoring break my Laravel app?
- The core is designed for fail-safe delivery and includes HTTP retry orchestration plus a locked local file buffer. That means events can be buffered and retried rather than forcing a synchronous failure path on every request. You should still validate the buffer path, permissions and disk capacity in your own deployment, and decide how much local backlog you are willing to retain.
- How does the locked local file buffer work and is it safe for production?
- The core owns a locked local file buffer as part of its delivery mechanism, which helps avoid concurrent write corruption when multiple PHP workers emit events. In production you need to ensure the buffer directory is writable by the PHP process, sits on reliable local storage, and is included in your operational monitoring. Treat an ever-growing buffer as a signal that export is failing rather than as normal steady state.
- Can I build a custom framework adapter with apirelio/php-core?
- Yes. The package documents direct extension points: implement Apirelio\Core\Contracts\IngestionClient and Apirelio\Core\Contracts\EventTransport, then use EventFactory with EventContext to produce the same ingestion payload as the official Laravel, Symfony and Nette packages. This is the intended route if your framework or internal platform is not covered by an official adapter.
- How should I test Apirelio event delivery without sending real traffic to the API?
- The core exposes IngestionClient and EventTransport contracts, so tests can bind fake or recording implementations instead of the real HTTP client. Build events through EventFactory with an EventContext and assert on the resulting payload, including privacy-filtered metadata and extracted error codes. The locked file buffer and retry orchestration can also be exercised with a local temporary directory and a stub transport.
- Does apirelio/php-core replace OpenTelemetry, Laravel Telescope or Sentry?
- No. It is a customer-aware API monitoring core for Apirelio's own event contract and delivery pipeline, not a general-purpose tracing, logging or error-tracking SDK. It can coexist with existing observability tools, but you should review middleware ordering, global hooks and outbound HTTP instrumentation so you do not double-capture or distort data. The README's scope is request and route adaptation, customer and application metadata, error codes and delivery.
- Is apirelio/php-core production-ready and actively maintained?
- The package is published on Packagist and documented as the core library behind the official Apirelio SDKs, with PHP 8.2 to 8.4 support. The README does not publish a formal support policy, so confirm the release cadence and maintainer commitments on the Packagist and GitHub pages before relying on it. Because telemetry is cross-cutting, pin a known-good version and test upgrades in staging.