Operations | Monitoring | ITSM | DevOps | Cloud

Imagine being one of the world’s largest banking institutions and experiencing a critical severity security incident that affects millions of customers and billions of dollars. Now imagine it takes 20 minutes from the first notification to log a response and track down all relevant information from a variety of global systems just to understand the context and nature of the incident.

To celebrate a 3-year integration anniversary between Cloud 66 and Vultr we’re showcasing some of the changes and improvements that we have implemented in both of our platforms. To show how well our platforms work together, we’re taking a Rails 7 application sample and walking you through how to containerize and deploy that application on Vultr with Cloud 66.

Separate “debug” and “release” builds are very common in embedded development. Typically the notion is improved debug capabilities (less aggressive compiler optimizations, more debugging information like logs) vs. highly optimized and hardened production release builds. I’m here to describe disadvantages to this practice, and why it might make sense to consolidate to a single build! Like Interrupt? Subscribe to get our latest posts straight to your mailbox.

JMX metrics give solid insights into the workings of your application. Integrating them with Levitate (our time series data warehosue) required us to jump some hoops with vmagent.