Because ESB was previously deployed by a vendor and is deployed on disk C (disk C has a small space, and many windows service logs of ESB are added on disk C, it is easy to fill up disk C space, this causes the ESB service to run down. An accident occurs almost every few weeks and requires manual intervention, which is not annoying). Therefore, the ESB built based on RabbitMQ was integrated some time ago.
Because ESB was previously deployed by a vendor and is deployed on disk C (disk C has a small space, and many windows service logs of ESB are added on disk C, it is easy to fill up disk C space, this causes the ESB service to run down. An accident occurs almost every few weeks and requires manual intervention, which is not annoying). Therefore, the ESB built based on RabbitMQ was integrated some time ago.
Because ESB was previously deployed by a vendor and is deployed on disk C (disk C has a small space, and many windows service logs of ESB are added on disk C, it is easy to fill up disk C space, as a result, the ESB service is down, and an accident occurs almost every few weeks, which requires manual intervention, which is not annoying). Therefore, the ESB built based on RabbitMQ was comprehensively optimized some time ago ,, to ensure the stability and reliability of the ESB service, an automated ESB monitoring and O & M system is initially established. This article introduces one of the technologies used in this system, SSIS is used to monitor the disk space of remote servers and send email alerts. The purpose is to perform manual intervention when automatic esb o & M fails.
WMI can easily query and obtain the disk space of the remote server. For example, if the disk space is less than 1 GB, an email is automatically sent to the Custom User for alarm. The procedure is as follows:
WMI Connection Manager:
Two defined package variables are as follows:
WQL statement Through WMI:
DeviceID