This month we launched CRMState.com a service that specializes in monitoring SugarCRM. There is a vast assortment of server monitoring solutions available but we ( Atcore Systems ) wanted to utilize our knowledge of SugarCRM to build a monitoring system that is application specific. The fact is that I can choose 1 of hundreds of server monitoring tools to monitor my server but none of them are SugarCRM aware. They don’t know the application, the features and all of the additional non standard types of monitoring and suggestions that can take place to enhance the software.
In version 1 we changed up the standard monitoring and instead of monitoring for the page to respond we verify that specific words show up on the login page. This insures that not only the server and database are up but that the page is showing as it should. It is in our roadmap to take on page checks to another level but we will talk about that in our next update.
Another monitor feature we added was fatal log alerting. Fatals shouldn’t happen very often, except in certain scenarios, if your SugarCRM instance is healthy. We monitor for fatals and alert the user based on their alert configuration. This may seem somewhat standard for a logging system but we have plan to take it much further in the near future.
Perhaps the biggest impact this has in relation to SugarCRM monitoring is that the service specializes in SugarCRM monitoring. With that focus we can continuously add SugarCRM specific checks, build in suggestions and keep up with the pace of SugarCRM releases.
- No public Twitter messages.