Ranetrace Documentation

Ranetrace watches a production app from both sides. From the outside it checks uptime, response time, certificates, domains, DNS, Lighthouse scores and broken links on any website, with no code to install. From the inside it collects errors, logs and events through an SDK you install in your app.

There are two SDKs, and they capture the same things:

• ranetrace/ranetrace-laravel for Laravel applications.
• ranetrace/ranetrace-php for any other PHP application.

The outside view is configured in the Ranetrace app and has no documentation page here. Everything below documents the SDKs, and only what has been verified against their source.

Getting started

• Introduction: the two SDKs, what each feature does, and how data reaches the API.
• Installation: install the Laravel package, add your key, and verify the connection.
• The worker: schedule ranetrace:work and run a queue worker (Laravel).
• PHP installation: install the framework-agnostic PHP SDK, bootstrap it, and flush its buffer.

Features in the Laravel SDK

• Error tracking: capture unhandled and reported exceptions.
• JavaScript errors: client-side errors via a single Blade directive.
• Centralized logging: a Monolog driver that ships logs to Ranetrace.
• Event tracking: record custom events with a hashed user agent and session id.
• Website analytics: privacy-first page-visit analytics with no cookies.

Features in the PHP SDK

• PHP error tracking: uncaught exceptions, fatal errors and manual reports.
• PHP centralized logging: a Monolog handler you add to your own logger.
• PHP event tracking: custom events with hashed visitor fingerprints.
• PHP JavaScript errors: a relay you mount yourself plus the browser snippet.