A Question about Uptime Monitoring using Patterns
Question asked by Ronald Raley - 8/9/2020 at 9:24 PM
Unanswered
A ping isn't good enough.  The mail server could still be offline.  So our uptime monitor can scan a website and look for HTML patterns indicating a service is online or offline.

However, when we scan the SmarterMail webmail login, the HTML code is exactly the same, always.  It remains the same even if SmarterMail is offline and presents a message to users on the screen.

The situation-at-hand is that this downtime message is not HTML that can be scanned.  It is deep within JS files that auto-populate DIVs.

Scratching my head on this one.  Does anyone know of a way to use plain old "pattern matching" on SmarterMail to determine if the server is alive or not?

Thanks,
Ron

3 Replies

Reply to Thread
0
Sébastien Riccio Replied
As far as I know, checking vit https will only check if IIS is running. As you stated the content returned by IIS is static and then from there it's based on API calls done by the browser.

You could maybe add an aspx page, something like check.aspx, and do from there a simple API call, for example, try to authenticate as a user used for the check and return SUCCESS / FAILURE depending the result of the call.

Then use your monitor tool pattern matching.

It's a bit unconvenient but I have no other idea ...
Sébastien Riccio
System & Network Admin

0
Ronald Raley Replied
Sébastien,

Thanks for your input.  I may have just figured it out!

We can hit the Diagnostic Page at /About/checkup which is wide open.  There are product checks at the bottom.

Passed    Activation ECHO A0
Passed    Activation ECHO A1
Passed    Connection to SmarterMail Service
Passed    Product Activated?
Passed    IIS Worker Count: 1

Now, I need to do some testing since I have never viewed this page when SmarterMail experiences issues.  In the past, web access has died yet MailService.exe continued to run.

Ron
1
Sébastien Riccio Replied
Damn, you're right. The page is wide open... Good thing for the checks, but I'm not sure it's a good idea to give too much informations about a system publicly.
I thought it was limited to the system admin... hum :)
Sébastien Riccio
System & Network Admin

Reply to Thread