Download the PHP package hamzi/corewatch without Composer

On this page you can find all versions of the php package hamzi/corewatch. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Example code of hamzi/corewatch

Informations about the package corewatch

Laravel CoreWatch 🛡️

Embedded DevOps dashboard for Laravel — monitor, debug, and operate your server without leaving your app

Latest Stable Version Build Status Total Downloads License PHP Version

Quick Start · Why CoreWatch? · Developer API · Architecture · Filament · Troubleshooting

[!IMPORTANT] CoreWatch is a self-contained server monitoring utility for Laravel applications. It provides real-time system metrics, log streaming, and operational controls without requiring external agents or daemons like Netdata or Grafana.

Why CoreWatch?

Problem CoreWatch Solution
"I need server metrics without external daemons" Reads /proc directly — zero background processes
"Log files are multi-gigabyte and crash web viewers" O(1) memory backward-seeking parser streams any file size
"I want safe administrative actions without shell risks" Whitelisted command keys only — no raw shell input accepted
"I use Filament or Livewire and need embedded monitoring" Livewire component and modular Blade partials
"I need alerts when CPU or RAM spikes" Scheduled health check with Slack, Telegram, and custom events
"Load balancer needs a health check endpoint" GET /corewatch/api/health returns 200 or 503

CoreWatch vs. Alternatives

Feature CoreWatch Netdata Laravel Telescope Grafana Agent
Zero external daemon ✅ ❌ ✅ ❌
Server metrics (CPU/RAM/Disk) ✅ ✅ ❌ ✅
Log file streaming ✅ ❌ ❌ ❌
Safe ops panel ✅ ❌ ❌ ❌
Laravel-native install ✅ ❌ ✅ ❌
Filament/Livewire embed ✅ ❌ ❌ ❌
Built-in alerting ✅ ✅ ❌ ✅

⚡ Quick Start (30 seconds)

Open /corewatch in your browser. That's it.

For production, add auth middleware in config/corewatch.php and schedule health checks:

System Architecture

The following diagram illustrates how CoreWatch handles data collection, log streaming, and alert dispatching:

🏗️ Package Architecture (Clean Architecture)

CoreWatch follows layered architecture with clear separation of concerns:

Layer Responsibility Example
Contracts Define abstractions SystemMetricsCollectorInterface
Domain Pure business logic HealthThresholdEvaluator
Application Orchestrate use cases GetServerMetricsAction
Infrastructure External I/O LogFileRepository, CpuMetricsCollector
Http HTTP boundary DashboardController (thin)

🧱 Modular @include Partial Architecture

CoreWatch separates all diagnostics into elegant, self-contained monospace tables inside resources/views/partials/. This modular structure allows clients to easily publish views and include specific tables anywhere inside their custom dashboards:

Partial Blade View Path Diagnostic Target Layout Display Style Customization Purpose
partials.cpu CPU Cores & Load averages Monospace Table Monitor core load thresholds (1m, 5m, 15m)
partials.ram System Memory (RAM) Allocation Monospace Table Track allocated, free, and available memory
partials.disk Disk Storage & Volumes Space Usage Table Monitor root storage partition size limits
partials.processes Top Linux processes Process Table Identify high CPU & memory processes
partials.database Database engine & size DB Status Table Track table counts and database size
partials.app-checks Application health checks Status Indicator List Verify Cache, Queue, and Security modes
partials.specifications Host specifications Specs Table Display PHP, OS, and server version info
partials.services Whitelisted service controls Action Table Safe execution of authorized commands
partials.logs Live log stream Log Console View and filter real-time logs with pagination

Key Highlights

  1. Light & Dark Theme UI: Self-contained Blade views with built-in Light and Dark themes. Built with Tailwind CSS and Alpine.js with zero bundler dependencies.
  2. Memory-Safe Log Streaming: Streams Laravel, Nginx, and Apache log files using backward chunked seeks ($O(1)$ memory usage) even on multi-gigabyte log files.
  3. Low-Overhead System Metrics: Reads /proc directly with shell command fallbacks to report CPU load, RAM allocation, disk capacity, and uptime.
  4. Whitelisted Service Controls: Safe execution of pre-configured administrative commands (queue restart, cache clearing) mapped to strict keys to prevent arbitrary command execution.
  5. Top Active Processes: Displays active Linux processes sorted by CPU and memory usage with PID and owner.
  6. Database Telemetry: Shows connection status, table count, and estimated database size for MySQL, PostgreSQL, and SQLite.
  7. Application Integrity Checks: Verifies cache store, queue driver, environment, and debug mode status.
  8. Livewire & Filament Support: Includes a Livewire component (<livewire:corewatch-dashboard />) for embedding into Filament and custom admin panels.
  9. Scheduled Health Alerts: Background command (corewatch:check-health) that evaluates resource limits and dispatches alerts to Slack, Telegram, or custom event listeners.
  10. Developer Facade API: Access metrics programmatically via the CoreWatch facade (CoreWatch::metrics(), CoreWatch::health()).
  11. One-Command Install: php artisan corewatch:install publishes configuration and displays a production checklist.
  12. Health Probe Endpoint: Built-in JSON health endpoint for load balancers (/corewatch/api/health) and Prometheus metric exporter (/corewatch/api/metrics/prometheus).

🛠️ Installation & Setup

Production Install (Packagist)

Publish Views (Optional — for customization)

Local Development (Path Repository)

Integration Options

CoreWatch supports multiple integration methods:

[!TIP] When including modular partials in a custom page, wrap them in the parent Alpine.js controller: <div x-data="corewatchDashboard()">...</div>.

Option A: Standalone Route

Navigate directly to /corewatch to access the full dashboard.

Option B: Modular Partials

Publish the views and embed specific partials inside existing administrative pages:

Option C: Blade Component

Embed the dashboard view directly:

Option D: Livewire Component

Embed the Livewire component in Filament dashboards or custom panels:

⚙️ Thresholds & Alerting

Enable real-time warnings on Slack or Telegram by configuring your host .env:

Register heartbeat and health checks in routes/console.php:

Diagnostic & Operational Commands

Verify your deployment and alert pipelines via Artisan:

👨‍💻 Developer API (Programmatic Access)

CoreWatch exposes a Facade and Manager for use in your own code, jobs, and custom admin panels:

Health Endpoint (Uptime Monitors / K8s Probes)

Returns 200 when healthy, 503 when thresholds are breached. Configure in .env:

Prometheus (Grafana / Monitoring)

Arabic Localization

Publish translations: php artisan vendor:publish --tag=corewatch-lang

Custom Alert Channels (Events)

Hook into threshold breaches in your AppServiceProvider:

Guide Description
Architecture Layer diagram, data flow, and extension guide
Filament Integration Embed in Filament admin panels
Troubleshooting Common issues and fixes
Deployment Production checklist
Contributing Development workflow and coding standards
Security Vulnerability reporting policy

🔒 Security Practices & Fallbacks

  1. RCE Protection: CoreWatch never accepts raw input strings to execute shell commands. It maps requests to rigid keys registered in config/corewatch.php and blocks any unauthorized requests.
  2. Memory Safety: The Log Parser uses direct fseek backward seeking to stream logs in 64KB blocks, maintaining a strict $O(1)$ memory consumption profile regardless of log file size.
  3. Graceful Fallbacks: If commands like exec or proc_open are disabled in php.ini, the package falls back to parsing native /proc direct files and displays interactive notifications.

📄 License

The MIT License (MIT). Please see License File for more information.

All versions of corewatch with dependencies

PHP Build Version
Package Version
Requires php Version ^8.2|^8.3|^8.4
laravel/framework Version ^11.0|^12.0|^13.0
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package hamzi/corewatch contains the following files

Loading the files please wait ...