PHPackages zhandos717/moonshine-monitoring - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Logging & Monitoring](/categories/logging) 4. / 5. zhandos717/moonshine-monitoring ActiveLibrary[Logging & Monitoring](/categories/logging) zhandos717/moonshine-monitoring =============================== Server monitoring for MoonShine with real-time resource usage tracking 06PHP Since Sep 27Pushed 7mo ago1 watchersCompare [ Source](https://github.com/zhandos717/moonshine-monitoring)[ Packagist](https://packagist.org/packages/zhandos717/moonshine-monitoring)[ RSS](/packages/zhandos717-moonshine-monitoring/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependenciesVersions (1)Used By (0) Moonshine Monitoring ==================== [](#moonshine-monitoring) Server monitoring package for MoonShine admin panel. Description ----------- [](#description) Moonshine Monitoring is a Laravel package that provides system resource monitoring capabilities for applications using the MoonShine admin panel. It tracks CPU, memory, and disk usage of your server and displays this information in an intuitive dashboard within MoonShine. Features -------- [](#features) - Real-time monitoring of CPU usage - Memory consumption tracking - Disk space monitoring - Data visualization in MoonShine dashboard - Command-line interface for manual data recording - Database storage of monitoring records - Automatic data purging based on configuration - Multi-instance support with instance naming - Pure PHP implementation (no shell scripts required) - Enhanced dashboard with progress bars and real-time updates - Multi-language support (English and Russian) Installation ------------ [](#installation) 1. Install the package via composer: ``` composer require zhandos717/moonshine-monitoring ``` 2. Publish the configuration file: ``` php artisan vendor:publish --provider="Zhandos717\MoonshineMonitoring\MonitoringServiceProvider" --tag=config ``` 3. Run the migrations: ``` php artisan migrate ``` 4. The monitoring dashboard will automatically appear in your MoonShine menu. Usage ----- [](#usage) ### Basic Usage [](#basic-usage) The package automatically adds a monitoring page to your MoonShine dashboard. You can configure whether this menu item is automatically added via the `auto_menu` option in the configuration file. ### Command Line [](#command-line) You can manually record resource usage via the command line: ``` php artisan moonshine-monitoring:record ``` ### Scheduling [](#scheduling) To continuously monitor your system, schedule the record command in your `app/Console/Kernel.php`: ``` protected function schedule(Schedule $schedule) { $schedule->command('moonshine-monitoring:record')->everyMinute(); } ``` Configuration ------------- [](#configuration) After publishing the configuration file, you can modify the settings in `config/monitoring.php`: - `auto_menu`: Whether to automatically add the monitoring page to the MoonShine menu - `instance_name`: The name of this monitoring instance (defaults to your app name) - `notifications`: Telegram notification settings (not yet implemented) - `migrations`: Enable or disable package migrations - `purge_before`: Automatically purge records older than this time period Dashboard Features ------------------ [](#dashboard-features) The updated monitoring dashboard includes: 1. **Real-time Resource Monitoring** - Visual progress bars for CPU, memory, and disk usage - Current usage percentage display - Auto-refresh functionality for real-time updates 2. **Historical Data Visualization** - Detailed table of historical monitoring records - Time-based sorting of records - Instance name identification 3. **User Interface Enhancements** - Multi-language support (English/Russian) - Responsive design for different screen sizes - Intuitive controls for data refresh Roadmap ------- [](#roadmap) ### Short-term Goals (v1.x) [](#short-term-goals-v1x) 1. **Complete Dashboard Implementation** - Add line charts for historical data visualization - Implement filtering by time periods - Add instance comparison capabilities 2. **Notification System** - Implement Telegram notifications for resource threshold breaches - Add email notification support - Create configurable alert thresholds 3. **Performance Improvements** - Optimize database queries for large datasets - Implement data aggregation for long-term storage - Add caching mechanisms for frequently accessed data 4. **UI/UX Enhancements** - Improve the visual design of metrics display - Add dark mode support - Implement responsive design for mobile devices ### Long-term Goals (v2.x) [](#long-term-goals-v2x) 1. **Extended Monitoring Capabilities** - Network usage monitoring - Process monitoring - Service status monitoring - Database performance metrics 2. **Advanced Analytics** - Predictive resource usage analysis - Anomaly detection algorithms - Usage pattern recognition 3. **Multi-server Support** - Centralized monitoring dashboard - Cross-server comparisons - Distributed monitoring agents 4. **Export and Reporting** - PDF report generation - CSV data export - Scheduled report delivery MoonShine 3.x Compatibility --------------------------- [](#moonshine-3x-compatibility) This package now fully supports MoonShine 3.x with the following updates: - Updated service provider for new MoonShine architecture - Compatible page and component implementations - Updated controller with proper JSON responses - Fixed debug code issues - Enhanced dashboard with historical data charts - Improved user interface with real-time updates Issues and Improvements Needed ------------------------------ [](#issues-and-improvements-needed) After analyzing the codebase and updating for MoonShine 3.x compatibility, here are the key technical issues and improvements needed: ### Resolved Issues [](#resolved-issues) 1. **Debug Code in Controllers** - Removed `dd()` statements from `MonitoringController` and `MonitoringComponent` 2. **Incomplete Implementation** - Enhanced controller to return proper JSON responses - Improved monitoring dashboard with historical data visualization 3. **Migration Registration** - Fixed migration registration in service provider - Added proper resource publishing configuration ### Remaining Issues [](#remaining-issues) 1. **Configuration Issues** - The notifications section in the config file is not implemented but has a placeholder - The purge functionality for old records is configured but not implemented 2. **Platform Support** - Shell scripts only exist for Darwin (macOS) and Linux, with no Windows support - The script resolution logic may not work correctly on all systems 3. **Code Quality** - Missing input validation in several components - Limited error handling in shell script execution - No unit tests exist for the package ### Enhancement Opportunities [](#enhancement-opportunities) 1. **Data Visualization** - Add more detailed historical data charts - Implement time range filtering for metrics - Add comparison capabilities between different time periods 2. **Performance Optimization** - Implement caching for frequently accessed data - Add batch processing for recording multiple metrics - Optimize database queries for large datasets 3. **User Experience** - Add customizable alert thresholds - Implement dashboard widgets that can be rearranged - Add export functionality for monitoring data Testing ------- [](#testing) The package includes comprehensive tests for all components: ``` # Run all tests composer test # Run tests with coverage composer test-coverage ``` ### Test Coverage [](#test-coverage) - Unit tests for all models, actions, and system resources - Feature tests for controllers and pages - Configuration tests - Shell script path validation ### Running Tests [](#running-tests) 1. Install development dependencies: ``` composer install ``` 2. Run the test suite: ``` ./vendor/bin/phpunit ``` ### Test Structure [](#test-structure) The tests are organized as follows: - `tests/Unit/` - Unit tests for individual components - `tests/Feature/` - Feature tests for integrated functionality - `tests/TestCase.php` - Base test case with package configuration ### Current Test Status [](#current-test-status) Currently, we have implemented: - Simple unit tests that don't require the full Laravel/MoonShine environment - Tests for system resources (CPU, Memory, Disk) - Tests for the MonitoringRecord model - Basic configuration tests Some tests that require the full MoonShine environment are currently failing due to dependency injection issues. These will be resolved in future updates. Contributing ------------ [](#contributing) Contributions are welcome! Here's how you can help: 1. Fork the repository 2. Create a new branch for your feature or bug fix 3. Write your code and tests 4. Submit a pull request with a clear description of your changes ### Development Guidelines [](#development-guidelines) - Follow PSR-12 coding standards - Write meaningful commit messages - Include tests for new functionality - Update documentation when needed - Ensure all tests pass before submitting a pull request ### Areas Needing Contribution [](#areas-needing-contribution) 1. **Windows Support** - Create PowerShell scripts for Windows systems - Test cross-platform compatibility 2. **Additional Metrics** - Network usage monitoring - Process monitoring - Custom metric support 3. **Testing** - Expand test coverage - Add integration tests - Set up continuous integration 4. **Documentation** - Expand usage examples - Add troubleshooting guides - Create API documentation Requirements ------------ [](#requirements) - PHP 8.2 or higher - Laravel 10.0 or higher - MoonShine 3.0 or higher License ------- [](#license) The MIT License (MIT). Please see [License File](LICENSE) for more information. ### Health Score 17 — LowBetter than 6% of packages Maintenance44 Moderate activity, may be stable Popularity4 Limited adoption so far Community7 Small or concentrated contributor base Maturity13 Early-stage or recently created project Bus Factor1 Top contributor holds 100% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Community Maintainers ![](https://www.gravatar.com/avatar/34606a1196769d7c9105372ab3321e9bacf6580ff5757e851da05c850b0239a0?d=identicon)[zhandos717](/maintainers/zhandos717) --- Top Contributors [![zhandos717](https://avatars.githubusercontent.com/u/64123073?v=4)](https://github.com/zhandos717 "zhandos717 (26 commits)") ### Embed Badge ![Health badge](/badges/zhandos717-moonshine-monitoring/health.svg) ``` [![Health](https://phpackages.com/badges/zhandos717-moonshine-monitoring/health.svg)](https://phpackages.com/packages/zhandos717-moonshine-monitoring) ``` ### Alternatives [psr/log Common interface for logging libraries 10.4k1.2B9.2k](/packages/psr-log)[itsgoingd/clockwork php dev tools in your browser 5.9k27.6M94](/packages/itsgoingd-clockwork)[graylog2/gelf-php A php implementation to send log-messages to a GELF compatible backend like Graylog2. 41838.2M138](/packages/graylog2-gelf-php)[bugsnag/bugsnag-psr-logger Official Bugsnag PHP PSR Logger. 32132.5M2](/packages/bugsnag-bugsnag-psr-logger)[consolidation/log Improved Psr-3 / Psr\\Log logger based on Symfony Console components. 15462.2M7](/packages/consolidation-log)[datadog/php-datadogstatsd An extremely simple PHP datadogstatsd client 19124.6M15](/packages/datadog-php-datadogstatsd) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)