Weave Code
Laravel Pulse Graphql Laravel Package
larassn/laravel-pulse-graphql
Laravel Pulse GraphQL adds GraphQL monitoring cards to Laravel Pulse, letting you track query counts, execution times, slow requests, and errors so you can quickly diagnose performance bottlenecks and regressions in your GraphQL API directly from the Pulse dashboard.
At a glance
Frequently asked questions about Laravel Pulse Graphql
- What is larassn/laravel-pulse-graphql used for?
- It adds GraphQL-focused monitoring cards to Laravel Pulse so you can see query counts, execution times, slow requests, and errors from your GraphQL API in the Pulse dashboard. It complements Pulse's default HTTP and database recorders, which tend to under-report resolver-level cost because many GraphQL operations share a single POST /graphql route. It is aimed at Laravel applications that expose GraphQL and already run Pulse.
- How do I install larassn/laravel-pulse-graphql?
- Install it with Composer using composer require larassn/laravel-pulse-graphql, then publish the package configuration if one is provided. Register the recorder or middleware in your GraphQL stack and add the card to your Pulse dashboard as described in the README. Because it is a standard Laravel package, the service provider is normally auto-discovered, but confirm the exact steps for your version.
- Which GraphQL implementations does larassn/laravel-pulse-graphql support?
- The public description does not name a specific engine, and the available release notes do not confirm whether Lighthouse, Rebing, or raw webonyx is instrumented. Verify this in the README or source before adopting, especially if you use Lighthouse and need resolver-level attribution. Treat GraphQL engine support as a hard requirement to confirm rather than an assumption.
- Does larassn/laravel-pulse-graphql support Laravel 13?
- Version 2.1.0 widened its Composer constraints to admit Laravel 13, which is a packaging change rather than an API change. That alone does not prove a green CI run against Laravel 13, so check the package's test matrix and PHP version requirements before relying on it. For existing consumers, the change implies no integration work.
- What overhead does larassn/laravel-pulse-graphql add in production?
- Resolver-level instrumentation sits in the hot path, so cost per request should be measured in your own environment rather than assumed. The package writes metrics into Pulse's storage, and it is worth confirming whether it honors Pulse sampling and Pulse::record throttling or records every operation. Start in staging with realistic GraphQL traffic before enabling it broadly in production.
- Does larassn/laravel-pulse-graphql store GraphQL query text or variables?
- The available context does not state whether the recorder captures only operation names or also full query text and variables. If text or variables are persisted, GraphQL payloads can carry PII and tenant identifiers into Pulse tables. Define retention and redaction explicitly and verify the behavior in the package source before enabling it on sensitive APIs.
- How does larassn/laravel-pulse-graphql handle GraphQL errors?
- GraphQL APIs often return HTTP 200 with an errors array, so status-code-based recording can misclassify failing operations as healthy. Confirm that the package classifies GraphQL errors separately from transport failures and surfaces them on the Pulse card. If it does not, a green dashboard may hide failing operations.
- Can I use larassn/laravel-pulse-graphql with Pulse sampling and throttling?
- Pulse supports sampling and record throttling, and the package should participate in those controls rather than writing unconditionally per operation. The supplied context does not confirm this, so check the recorder implementation and configuration. If it writes unconditionally, account for the extra storage and write load at high GraphQL volume.
- How do I add the GraphQL card to my Laravel Pulse dashboard?
- The package's Pulse card is registered where your dashboard is defined, which is typically the published Pulse dashboard view and may also involve package configuration depending on version. Follow the exact card class name and snippet in the README, then clear your config and view caches. Load /pulse and confirm the GraphQL card renders with data from recent operations.
- Is larassn/laravel-pulse-graphql actively maintained, and what are the alternatives?
- It is a single-maintainer package with a small contributor base and a relatively thin release history, so bus factor is a real consideration. If you need a broader telemetry strategy, OpenTelemetry-based tracing may be a better fit, while Pulse's default recorders cover HTTP and database metrics but not resolver-level GraphQL cost. Review issue responsiveness, release cadence, and dependency drift before standardizing on it.
Weaver
How can I help you explore Laravel packages today?