Weave Code
Monitor Laravel Package
orchid/monitor
Monitor your Laravel application from inside the Orchid admin panel. orchid/monitor gathers health checks, server metrics, logs, and runtime performance into one dashboard, so you can spot issues early and keep your app running reliably without switching between tools or services.
Monitor will show you current information about your system
Frequently asked questions about Monitor
- What is orchid/monitor and what does it do?
- orchid/monitor is the system-information screen bundled inside the theOrchid/Platform monorepo. It gathers health checks, server metrics, logs, and runtime performance into one dashboard inside the Orchid admin panel. It is intended to give you a quick readout of your system without switching between tools.
- Can I install orchid/monitor as a standalone Composer package?
- No. There is no independent Composer artifact, release cadence, or version constraint for orchid/monitor. It ships as part of Orchid Platform, so the unit of adoption is the full admin panel, not a single monitor package. You cannot composer require it on its own.
- How do I install orchid/monitor in a Laravel application?
- You install Orchid Platform, and the monitor screen is included as part of that admin panel. The screen registers itself and inherits the panel's middleware, layout, navigation, and permission model. There is no separate installation step for the monitor itself.
- Which Laravel versions does orchid/monitor support?
- Laravel compatibility follows the Orchid Platform release you pin, not an independent orchid/monitor version. There is no separate changelog or version constraint for the monitor screen. Check the Orchid Platform tag you are installing to confirm Laravel version support.
- What system metrics does orchid/monitor display?
- The screen surfaces CPU, RAM, and disk information through an exposed Monitor service with cpu(), ram(), and disk() methods. It also shows host system information, logs, and runtime details. You can call the Monitor service from your own Orchid screens or a small JSON endpoint if you need the values elsewhere.
- Why does orchid/monitor show 0% CPU or empty gauges?
- The monitor depends on shell calls such as exec, proc_open, and shell_exec to read system values. On hardened PHP-FPM images where those functions are disabled, the screen renders zeros or empty gauges instead of raising an error. Verify in the production runtime that those functions are actually available before relying on the output.
- Does orchid/monitor work correctly in Docker or Kubernetes?
- The monitors are Linux-shaped, and macOS or Windows will produce wrong or missing values. Inside containers, /proc and df reflect the container's view rather than the node's, and memory figures ignore cgroup limits. If you run containers, label these numbers explicitly as container-scoped or they will mislead.
- Is it safe to expose orchid/monitor in the admin panel?
- The page fingerprints the host, including kernel, PHP configuration, and database connection details. Broad admin access to it is a security finding, not a cosmetic issue. Confirm the route inherits your real auth guards, SSO, and IP allow-lists, and restrict it by Orchid role.
- Can orchid/monitor replace Pulse, Horizon, Telescope, or Sentry?
- No. orchid/monitor has no history, retention, alerting, error tracking, or uptime monitoring. It is a point-in-time system readout inside the admin panel, not a monitoring platform. Document clearly where Pulse, Horizon, Telescope, Sentry, or your APM own the questions this screen cannot answer.
- Is orchid/monitor actively maintained and safe to depend on in production?
- Maintenance moves with Orchid Platform releases, and there is no independent changelog, Stack Overflow corpus, or third-party documentation for the monitor screen. It has negligible standalone traction and zero dependents, so there are few external answers when it breaks. Never put it on a critical path, especially not as the tool an on-call engineer needs during an incident.
Weaver
How can I help you explore Laravel packages today?