Download the PHP package jenner/log-monitor without Composer
On this page you can find all versions of the php package jenner/log-monitor. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download jenner/log-monitor
More information about jenner/log-monitor
Files in jenner/log-monitor
Package log-monitor
Short Description monitoring and alerting of error log
License MIT
FAQ
Example:
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 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.
Informations about the package log-monitor
log-monitor
An active log monitor based on the tail command.
Why use log-monitor?
Sometimes we want to know what is happening when crontab task is running or what errors had been written into the php error log by php script, and we want to know quickly. log-monitor can help you to monitor the log and notify the users who want to know.
What can log-monitor do?
- monitor the log by the tail command
- notify users when there is an error
- custom log filter interface, which will check the log is error or not
- custom notification interface, which will notify the users
- custom reader interface, if you do not want to use the tail command
How to use log-monitor?
talk is cheap, show you the code:
There are three interfaces:AbstractReader, NotificationInterface, FilterInterface.
If you want to read log for somewhere else, you can create a class which extends AbstractReader.
If you want to filter your log in different way, you can create a class which implements FilterInterface.
If you want to send message to somewhere else, you can create a class which implements NotificationInterface.
How it works?
When you have created a MonitorTask object and call the run method,
it will start a sub process and call the tail command in the sub process. Then it will
read from the pipe and check the log by filter that if it is error or not. If there is an
error, it will call the notification to notify the users who want to know.
Just do not forget to call wait method to wait the sub process.
If you have many logs to monitor, you can use the Monitor to manage them. show you the code:
Just remember that when you call the start method, do not forget to call wait method.
