Operations | Monitoring | ITSM | DevOps | Cloud

For DevOps teams, delivering quality software has long required reconciling a major tension: In a perfect world, you’d catch every issue in each new release of your application before you deployed the release into production. But in the real world, doing so is tricky, not least because it’s hard to collect data about application performance before the application is actually deployed.

Hey Civo users, at Gimlet, we think that best practices in the Kubernetes ecosystem have solidified so much, that they can be packaged into tools, so that you don't have to make nuanced decisions every corner. This is what we have been doing with our CLI tools, and nowdays doing with the Gimlet Dashboard! We have been following Civo for over a year now and see how much the Gimlet team shares the Civo community's spirit.

Now that development teams know about CI/CD, there is no reason for deployments to become a time-consuming and cumbersome process. CI/CD may start with continuous testing, but adding automated deployments takes your CI/CD practice to the next level. Continuous deployment slashes the time it takes to release so you can spend more time improving the quality of your applications.

Real User Monitoring (RUM) gives you visibility into the behavior of your users and the performance of your applications. You may already be using RUM monitors to automatically notify your team when the number of RUM events—such as pageviews, clicks, or errors—rises above a threshold you define.

At incident.io, we pride ourselves on providing a great product to our customers. We’re also a small team, so we move fast and (whisper it not) occasionally break things. To mitigate the impact on our customers, we have our app set up so that every time our application raises an error (via Sentry), we get paged.