- How do I install maantje/pulse-database in a Laravel application?
- Install it with Composer, then let Laravel package auto-discovery register the service provider. Register the card in your Pulse dashboard configuration and optionally publish the package config if you need to customize it. No application code changes are expected, so the rollout stays limited to the Pulse dashboard setup.
- Which Laravel, PHP, and Laravel Pulse versions does maantje/pulse-database support?
- The repository's composer.json constraints are the authoritative source for supported Laravel, PHP, and Pulse versions. Check them against your application before installing and pin the package version in composer.json. Re-check compatibility before upgrading Laravel or Pulse, and validate the card in staging first.
- What database metrics does this Laravel Pulse card show?
- The card surfaces database health and performance metrics including query throughput, slow queries, connections, and transaction activity. It is designed to help you spot bottlenecks in real time on the Pulse dashboard. It complements rather than replaces APM, database-native monitoring, or alerting.
- Does the card support multiple database connections and read replicas?
- The overview does not confirm multi-connection or read-replica support, so treat this as something to verify before production rollout. Test it in staging against your actual connection configuration, including read/write splitting and non-default ports. If your topology is complex, confirm behavior with the maintainer or review the source.
- Does maantje/pulse-database run live queries against my database or read Pulse data?
- The overview does not state whether the card executes live queries or reads from Pulse's stored data, so verify this in the source and docs before relying on it. In staging, watch database query logs while the dashboard loads to see what the card actually does. This also informs the database privileges you need to grant.
- What database permissions does maantje/pulse-database require?
- Required privileges depend on whether the card reads Pulse's storage tables or queries the database directly, so confirm that first. Grant the least privilege needed and avoid using write or admin credentials for dashboard monitoring. Validate the setup in staging with the same database user you plan to use in production.
- Does the card expose query text, hostnames, or credentials on the Pulse dashboard?
- Review exactly what the card renders before adding it to a shared or production dashboard. Pulse dashboards should sit behind your existing authentication and authorization, and database details should only be visible to the intended audience. Never expose the dashboard publicly, and confirm that no credentials are displayed.
- Do I need Laravel Pulse installed to use maantje/pulse-database?
- Yes, this package is an additive card for Laravel Pulse, so Pulse must already be installed and operational. If your team is not using Pulse, treat Pulse adoption as a separate decision rather than bundling it with this card. The card fits best in an authenticated internal observability dashboard.
- Is maantje/pulse-database safe for production and what is the performance impact?
- The card is dashboard-scoped, so its blast radius should be limited to the Pulse dashboard rather than production traffic. The main operational concern is dashboard query load and refresh behavior, especially on busy databases. Pin the version, validate in staging, and monitor the dashboard after rollout.
- Is maantje/pulse-database maintained, and what happens if it is abandoned?
- It is a community package with a small maintainer base and no vendor SLA, although the recent 2025 release is a positive signal. Ongoing maintenance is low, but you should track releases and compatibility with Laravel and Pulse upgrades. Because it is MIT licensed, you can fork or vendor it, or replace it with a small in-house Pulse card if it becomes stale.