Additional Monitors for EC2 Instances

Ylastic now has additional monitors for keeping an eye on those EC2 instances.

HTTP
HTTPS
HTTPS Strict Check - the SSL certificate CN and the hostname must match
SSH
Ping
DNS resolution for the instance public address
Reverse DNS resolution for the instance elastic IP address

You can get the alerts for these monitors any way you want. Here is a sample email alert.

Here is an alert via twitter as viewed in Twhirl.

These are in addition to the AWS resources you can already monitor with Ylastic.

EC2 Instances
RDS Databases
EBS Volumes
AWS Service Health
Usage Costs
Scaling activities
Load Balancers

Sep 13, 2010

heleni_dev said...

Suggestion: For HTTP and HTTPS it would be very useful if we could specify a specific URL (like a heartbeat URL) and apply the following logic in your side: If the HTTP status code is 200 then mark the service as alive, if the HTTP status code is 40x, 50x, etc. then mark the service as dead.

ylastic said...

Yes. We are working on adding more specificity to allow one to pass in heartbeat urls. Coming soon!

Tracking this suggestion on the support site - http://support.ylastic.com/discussions/suggestions/98-hearbeat-urls-for-http-...

kweiner said...

Very nice! We might not need to keep our Pingdom service once heartbeat URLs are supported. BTW, the permalink for this article wasn't working for me: http://blog.ylastic.com/service-checks-for-ec2-instances

Seems like Posterous is once again having issues. It seems to periodically return the page. Keeping an eye on it. Thanks!

Sep 14, 2010

Added heartbeat URLs in today's release - http://support.ylastic.com/discussions/announcements/106-new-release-septembe...

ylastic blog