Documentation/SDK documentation

SDK documentation

Choose your implementation.

Start with your language, then open the framework guide that matches the application you want to monitor.

3 framework SDKsPHP packages 0.2Production ready
01

Implementations

Pick the shortest path to production.

All official PHP integrations share the same telemetry contract. Choose a framework adapter for automatic request tracking, or use PHP Core when building a custom adapter.

02

Architecture

One pipeline, native integrations.

Framework packages understand native routes, requests, dependency injection and background workers. PHP Core handles the stable event shape, privacy filtering, retry and local buffering.

Telemetry flowbash
Your application
  → framework SDK
  → privacy-safe event
  → Apirelio ingestion
  → customer integration analytics

Framework native

Use middleware, kernel events or Nette lifecycle hooks instead of custom instrumentation around every controller.

Customer aware

Resolvers attach a stable B2B customer and consuming application to normalized endpoint metrics.

!

Fail-safe

Telemetry failures never change the observed API response or hide its original exception.

03

Comparable data

The same event in every framework.

customer_idB2B account using the API
application_idSpecific consuming integration
method + routeNormalized endpoint identity
statusHTTP outcome
duration_msServer-side duration
api_versionVersion supplied by the consumer
releaseServing application deployment
error_codeStable diagnostic code
Privacy boundary

Bodies, credentials, cookies, query strings and client IP addresses are not part of the analytics event.