[This is a guest blog post from Shane Duan, product manager of Cloud Monitoring at Rackspace. We appreciate his help in making this integration happen!]

Logo_lockup_version-2 SPOT

We are proud to announce the release of an integration between Rackspace’s Cloud Monitoring and VictorOps. Our users will get reliable, flexible alerts and have the ability to manage them efficiently. Each product already has a lot of features to make it stand out in the crowd. The integration provides a more complete solution that you need to manage your infrastructure.

The integration itself keeps reminding me of the script I use to find the latest daily data dump file for analysis:

shane_blogpost3

When VictorOps’ VP of Operations, Tom Hart reached out to me the day after I responded to the integration request from a user, I knew already this was going to be a smooth integration between two products that follow the Unix philosophy.

According to Wikipedia, “The Unix philosophy emphasizes building short, simple, clear, modular, and extensible code that can be easily maintained and repurposed by developers other than its creators. The Unix philosophy favors composability as opposed to monolithic design.”

This is what came to my mind after signing up for the free VictorOps trial account and configuring it for my servers. With Cloud Monitoring focused on collecting metrics and sending alerts, it made perfect sense to integrate through notification plans and leverage VictorOps’ capability to combine people and data. This is the same reason that we use Mailgun for alert emails. As Cloud Monitoring scales, with composition through REST API calls, we can rely on the growth of other products to achieve reliability and performance.

We were able to meet several times through Google hangout and collaborated remotely between three cities and two continents (one of the engineers working on this integration is in Europe). VictorOps also paid a couple of visits to the Rackspace San Francisco office during their trips to the city for various conferences.

Finally, we are all very happy to have this first release through a new notification type in Cloud Monitoring called “victorops”. The victorops notification takes an API key and a routing key.

shane_blogpost1

As Cloud Monitoring detects issues and clears alarms, VictorOps will open and resolve incidents based on the alerts from Cloud Monitoring.

shane_blogpost2

For those who have found it valuable to have the traceroute and host CPU/Memory hog information in the email alerts, you can put both the email notification and VictorOps notification in the same notification plan and get all the information that you need. In the meantime, we are working on improvements to make them even more usable.

As Cloud Monitoring continues to focus on being the platform to collect data, process data and send out alert with the most reliability, efficiency and flexibility, VictorOps users will expect an on-call experience that keeps improving over the time.

As always, we love to hear from you! Please provide your feedback through our feedback portal or join the conversation on IRC (freenode #cloudmonitoring).