Weave Code
Site Monitor Laravel Package
capell-app/site-monitor
A Laravel package for monitoring the health of your sites. Run uptime and HTTP checks, track response status and performance over time, and surface problems early through the Capell admin panel, so you can catch outages and regressions before your users do.
External uptime, certificate, domain, and incident monitoring for Capell sites.
Frequently asked questions about Site Monitor
- How do I install capell-app/site-monitor in a Laravel app?
- Install it with composer require capell-app/site-monitor, then publish the package config and run migrations. After that, define your monitor targets, choose probe intervals, and make sure a scheduler and queue worker are running. The package is designed for a standard Laravel deployment rather than a separate monitoring service.
- What exactly does capell-app/site-monitor check?
- The package covers uptime and HTTP checks, response status and performance history, plus certificate, domain, and incident monitoring for Capell sites. It surfaces results in the Capell admin panel so problems appear before users notice them. Content assertions and DNS-specific checks are not confirmed in the available material, so verify the exact probe types in the config and source.
- Which Laravel and PHP versions does site-monitor support?
- The provided release material does not list supported Laravel or PHP versions, and the README excerpt is empty. Check the package composer.json on Packagist or GitHub for the require constraints and tested database drivers. Version 1.1.0 is the first stable release, promoted from 1.1.0-beta.46.
- Where do the uptime probes run: scheduler, queue worker, or external runner?
- The architecture points to an in-process scheduled command or queue job that performs probes from your application host. Whether external or distributed probing is supported is the largest architectural unknown and should be confirmed before relying on it for outage detection. In-app probes will report down when the platform itself is down.
- Can I use capell-app/site-monitor outside Capell in a plain Laravel app?
- It is built for the Capell ecosystem and assumes Capell conventions, including its admin panel. Adopting it in a plain Laravel app may pull in assumptions that are awkward to unwind. Evaluate the coupling before choosing it over a standalone Laravel uptime package.
- How do I stop site-monitor check history from growing forever?
- Check results accumulate on a schedule proportional to targets times frequency, so history tables can grow steadily. Configurable retention and pruning are not confirmed in the available material. Review the published config and migrations, and add a pruning job if the package does not ship one.
- Which alert channels and flap suppression does site-monitor support?
- The available material does not confirm which alert channels ship or whether deduplication and flap suppression exist. Notification wiring is part of the integration work, so verify mail, Slack, webhook, or SMS support in the config and docs. Without flap suppression, expect repeated alerts during intermittent failures.
- Is upgrading from 1.1.0-beta.46 to 1.1.0 a breaking change?
- There were 46 beta releases and the 1.1.0 release note only links to a compare view, so the beta-to-stable delta is not documented. Treat the upgrade as potentially breaking if you piloted a beta. Test the upgrade in staging and review the compare link or any upgrade guide before production.
- Is capell-app/site-monitor a good alternative to UptimeRobot or Pingdom?
- It duplicates rather than complements external synthetic monitoring such as UptimeRobot, Pingdom, or Checkly. Its strength is native Capell admin integration for site health and incident visibility. Its weakness is probe origin: monitoring from inside the app fails when the app or host fails, so keep an external monitor for true outage detection. Production readiness also depends on license, maintainer activity, and test coverage, which are not established in the available material.
- What are the SSRF and security risks of letting admins add arbitrary monitor URLs?
- Outbound HTTP from application servers raises SSRF, firewall, proxy, and egress concerns, especially if non-engineers can register arbitrary targets in the admin UI. Restrict who can add targets, validate URLs, and block internal IP ranges and metadata endpoints. Also confirm how probe credentials are stored and scoped.
Weaver
How can I help you explore Laravel packages today?