Dear Monitis support,
recently, we had a live chat with one of your supporters. We had a discussion regarding the SSL check. It does not seem to work on some of our external URLs.

We went through some painstaking analysis efforts. Hiwever, we were able to determine that it looks like your platform implementation does not seem to work correctly.

Reasoning:
Please try to set up a URL monitor, SSL check or whatever to ***.exchange.it (This is not the actual URL - we masked it). You will not be able to get results. The port 443 is available but you are not able to start the tls session.
The reason is: You seem to expect a http answer but the service will not deliver such. However, the TLS sessin "can" be established.

We did a proof of concept with one of our private monitoring instances. It is based on a nagios derivative and it is also not able to connect via it's built in check_http or check_tcp command. We then implemented check_ssl_cert (https://github.com/matteocorti/check_ssl_cert) . This check "is" able to check the service certificate.

Printout normal check:
Cannot make SSL connection.

Printout of check_ssl_cert:
SSL_CERT OK - x509 certificate '***.exchange.it' from 'Trusted Secure Certificate Authority 5' valid until Mar 26 23:59:59 2019 GMT (expires in 33 days)

Please reimplement your SSL check since it is based on an old codec.

I've been using the free test account and I love it. So I went to upgrade to a paid account however I can't get the monitoring I need because it falls below the minimum threshold.

I love this service – very easy to use, great functionality and a clean, good looking UI – I’d be really disappointed if I can't use it because of this technicality.
There are not many businesses out there that won't accept money from their customers when the customer actually want's to pay them for a service!

I have 4 websites I need monitored from three locations.

Any chance of a change here?

I have about 90 Monitors and have created a Custom Outage report for each - Very Painful tedious process -

Since several Monitors are in fact the same client on different products I need to be able to generate a single report that contains 1..X monitors - Also I need to group Outage Monitors by Product, region and so on. With the current functionality I will have to generate all the individual reports and then craft the consolidated report. I need this to contain - total summary of the grouping - with outage details. I would like to eat my cake.

currently when a SIP check failed, we only receive a email notification stating that there was a problem
i would like to see added the "SIP" OPTIONS message that was SENT to the Endpoint being monitored,... its useful when i want to look back at my SIP Endpoints and see how long it took for a reply to be sent, and i can further review whats taking the server so long to respond... currently i dont know which OPTIONS message i need to review, because i dont have the Call-ID of the OPTIONS call etc

having a traceroute also show you the details of the actual PING that failed would also be helpful, currently we only receive an alert that ICMP was down, we dont know where it timed out etc,,, and the URL thats included in the problem alert email, only shows the traceroute created AFTER it failed, which at that point its already working again, since it was a very short hiccup..