Chronosphere Platform

- Their customer success team is strong and really listens to feedback, gives clear indications on what they can address and what runs counter to their long-term goals, and they always follow up to ensure any issues or feedback has been resolved. - Recommendations are great, we manage the observability stack across a large number of teams and orgs and most do not have deep experience in this area which leaves us with a lot to manage. Tools that let us see the utility score of any given metric/label and give us the ability to create drop rules for those with no value allows us to respond in the moment and without a long feedback loop to address issues. - Quotas / pools give us flexibility to control and group workloads by both impact and criticality, allowing us to create buffers for other parts of the business that are less consistent with their sending needs and patterns.

It was very intuitive from my perspective and will be really useful for teams once adopted. * Easy to create a SLO SLI

Acceptance/utilization of open standards and open source tooling as a first class citizen made it really easy to adopt and train our users on how to use it. Chronosphere has also done an awesome job taking our feedback and turning relevant feedback into feature requests that we've gotten to see enter the platform, which is really cool.

- The current billing model is complex and requires deep thinking to understand the trade-offs - The cardinality model, while understandable, is painful to interact with - Platform offerings are increasingly dependent on using most, if not all, of their product offerings. This makes it hard to bring incremental improvements while working in a complex multi-vendor environment.

I don't think there's much to comment on the functionality since our org doesn't use it actively for our services. It would be nice if users can add customizations (cover page, just visual) to their SLO dashboard since it's their Service's health indicator, and people should feel a sense of attachment to it.

Making the jump from other platforms which have different standards regarding visualization, rolling up of metrics etc that are not transparent to the end user was definitely a growth moment for us, and required some help from Chronosphere. We're still getting the hang of how best to leverage the control plane options available to get the most out of it, but these are good problems to have, in my opinion.