Because we know simply creating SLOs is not enough, our team also dedicated itself to finding new ways to better extract insightful information from those SLOs. One of the major outcomes of this effort was the extreme revamp of our SLO Insights page. The main driver of this revamp was to abstract the technicalities behind SLOs and translate them into easy to understand, actionable information.

‍

We added intuitive and dynamic descriptions to every chart to help users more easily interpret what they’re seeing. This provides users with a clearer picture of how an SLO is being impacted and allows them to translate that impact into actual customer experience in an intuitive way. More specifically, we facilitated the interpretation of error budgets and burn rates by extrapolating insights such as telling users when an SLO is expected to miss its goal or identifying the periods of downtime that affected the greatest amount of end users. This makes it so that users can drive real action regarding preemptively tackling reliability issues and more confidently decide on what development initiatives to prioritize.

‍

Another outcome of our effort to extrapolate actionable data from SLOs was the development of the first version of the Summary Dashboard. As the name suggests, this dashboard provides an overview of how an application is behaving based on SLO performance and allows for identifying areas of the application that might require some extra attention. We divided the dashboard into three distinct sections: Summary, Application Performance and Reliability Breakdown.

‍

The Summary section shows everything that requires attention either immediately, or in the near future, displaying the number of SLOs being impacted at the moment and how many alerts are currently firing. The Application Performance section displays a breakdown of the application’s performance by building upon the information displayed in the Summary section. It shows which specific areas of an application are currently being impacted and what are the top underperforming areas. The Reliability Breakdown section displays a full performance breakdown of the entire application from the perspective of the SLOs that cover the application’s services.

‍

You asked and we delivered! As we gathered more and more feedback from our prospective customers about our platform, one thing became obvious: we needed to increase our data source offering to be able to integrate with existing monitoring stacks. During this past quarter, we increased our data source offering with the introduction of three new popular integrations.

‍

The first integration we worked on was New Relic. If you’re part of the IT Operations world, you’ve surely heard about this very popular monitoring tool. Our users can now use the monitoring data they are collecting through New Relic to set up SLOs inside Rely.io and start generating actionable and customer-focused insights from them.

‍

The next integration we worked on was the GCP integration. As per Google’s own statement, GCP’s Cloud Monitoring offers automatic out-of-the-box metric collection for Google Cloud services while also supporting monitoring of hybrid and multi-cloud environments. This made this integration to be next in-line for development as it’s a product widely used by organizations of all sizes

‍

Finally, by the end of the quarter we began working on allowing integrations with one of the most widely used and far reaching monitoring solutions: Prometheus. More specifically, the Prometheus Remote Write integration. This integration was heavily requested by our customers since many already use Prometheus to instrument and collect monitoring data from their applications but didn’t want to use our already supported Prometheus HTTP API integration, since it poses a security concern for many. By allowing remote write integrations, our users can selectively export the data most relevant to their SLO use cases without the need to deploy any public-facing endpoints that could compromise their application’s security and risk exposing sensitive information.

In retrospect, it was a tough but successful quarter in terms of product development. But this is just the beginning! We are continuing to improve on our current offering to address evolving client requirements and are already developing new amazing features like reliability reporting and error budget alerting that will boost the value our users can extract from the Rely.io platform.

‍

If you’d like to try out our product, join our upcoming Open Beta program where you’ll have first hand access to all these features and more, and will get the chance to contribute and tailor our roadmap according to your needs!