 07/08/2009 at 10:49
[Edit Comment]
I’ve had issues where the crawler doesn’t always auto-update and thus doesn’t pick up the new features when they are available. Can you comment on the resiliency of the auto-update mechanism to ensure it is always functional? Also, can you consider adding in a feature where the crawler will send out an alert email notification in case it encounters an error, such as auto-update failure or failure to connect to Paglo servers for a specified period of time? This sort of thing is really helpful when you are an independent IT professional supporting multiple clients. The crawler is great, but I’ve run into situations where it requires manual intervention on a near monthly basis. Ideally the crawler should be a set it and forget it service…since it should be controllable from the Web UI. |
We are going start posting quick hitting FAQs about Paglo. These are based on real customer questions and are useful to publish for everyone who is interested in Paglo and our IT Management SaaS platform.
Question
How resilient is the Paglo Crawler?
Answer
The Paglo Crawler is designed to be as fault tolerant as possible and is built in a similar way to the Google Chrome browser. This is the reason that there are multiple Crawler processes. The CrawlerExecutive process monitors the other Crawler processes and restarts them if necessary. If communication is lost with your Paglo account, then the Crawler will store timestamped data on disk until connection is re-established. This also applies to log data sent through the Crawler as well.
