- How do I install ranetrace/ranetrace-laravel in a Laravel application?
- Install it with Composer by requiring ranetrace/ranetrace-laravel, then publish the package configuration and add your Ranetrace credentials to the environment file. The package works as Laravel-side telemetry, so it also needs a queue worker running to ship ingest batches. After that, run the package's diagnostic Artisan commands to confirm connectivity and start seeing traces and errors in the Ranetrace dashboard.
- Does ranetrace/ranetrace-laravel slow down my Laravel requests?
- The package is built for lightweight request tracing with negligible overhead: it instruments the request and ships telemetry batches through a queue worker instead of blocking the response. Because ingest is queued, the network call to Ranetrace does not sit in the user-facing request path. As with any instrumentation, benchmark it in staging against your own workload before enabling it everywhere.
- What does Ranetrace for Laravel actually monitor?
- It covers error tracking, website analytics, uptime monitoring, and performance checks, with request tracing focused on catching slow queries and bottlenecks before users notice them. Traces and errors are batched and sent to the Ranetrace ingest endpoint from your Laravel application. The package is the integration layer only; dashboards, alerting, and the hosted MCP endpoint all live on the Ranetrace side.
- Do I need a queue worker to use this package?
- Yes. The architecture is application-side ingest: the package instruments your Laravel app, collects telemetry, and ships ingest batches through a queue worker. Without a running worker those batches are never delivered. Make sure your queue is supervised in production, the same way you would treat jobs, mail, and notifications.
- Which Laravel and PHP versions does ranetrace/ranetrace-laravel support?
- The package is distributed through Composer and targets standard Laravel applications, so the authoritative answer is the require block in its composer.json on the GitHub repository. Check that file for the exact PHP and illuminate/support constraints before adding it to your project. If you maintain several Laravel versions, confirm the constraint covers each one, especially older or LTS branches.
- How do I connect Claude Code, Cursor, or VS Code to Ranetrace over MCP?
- Create a token on the Ranetrace /mcp page, then add an HTTP MCP server entry pointing at https://api.ranetrace.com/mcp with a bearer authorization header. Claude Code, Cursor, and VS Code are explicitly supported clients. All 31 tools, their names, parameters, and output are unchanged from the previous embedded server, so existing agent prompts and workflows should keep working.
- What changed in v1.1.1 and where did the local MCP server go?
- v1.1.1 removes the embedded local MCP server, so your application no longer runs an MCP process and the package no longer depends on laravel/mcp. The MCP query surface moved to a hosted Streamable HTTP endpoint at https://api.ranetrace.com/mcp with the same 31 tools. To migrate, delete the ranetrace.mcp config block, remove RANETRACE_MCP_ENABLED and RANETRACE_MCP_TOKEN from your environment, drop laravel/mcp if nothing else needs it, and update your MCP client configuration. This shipped as a breaking change in a patch release, so pin your version deliberately.
- Is it safe to upgrade ranetrace/ranetrace-laravel to v1.1.1 in production?
- The application-side code change is small, but it is a breaking change delivered in a patch version, which is a release-governance risk rather than a technical one. Upgrade in a non-production environment first, confirm the app boots and ingest still works after removing the config block and env vars, and check that no scripts parse MCP rows from ranetrace:status or ranetrace:test. Also verify that removing laravel/mcp does not break a transitive dependency elsewhere in your applications.
- How do I verify Ranetrace is working in my Laravel app?
- The package ships diagnostic Artisan commands, ranetrace:status and ranetrace:test, which validate configuration and connectivity. If you have runbooks or CI scripts that parse their output, review them after moving to v1.1.1 because MCP-related rows were removed from those diagnostics. Pair the commands with a real request in staging and confirm the trace shows up in the Ranetrace dashboard.
- What are the alternatives to ranetrace/ranetrace-laravel?
- Common options in the Laravel ecosystem include Sentry or Bugsnag for error tracking, Laravel Telescope for local debugging, and hosted APM services for performance and uptime. Most of those require stitching together separate products for errors, analytics, uptime, and performance, whereas Ranetrace bundles them behind a single integration. If you specifically need MCP tooling inside your application runtime, note that v1.1.1 moved that surface to a hosted endpoint, which may not suit air-gapped or restricted-network environments.