Revinate, a company providing software services to hotels, was facing challenges with its growing customer base. The company's configuration had grown quickly to 25 physical servers supporting 400 virtual instances. The company's Software-as-a-Service (SaaS) offering is hosted in a Rackspace Private Cloud (RPC) environment that utilizes the OpenStack architecture. However, the RPC offering lacked the robust management capabilities needed for efficient operation. The available data came only infrequently in the form of a weekly email, forcing the company to track any trends manually. The company needed a tool that would enable them to instrument the entire stack from top-to-bottom, including the applications, all underlying services, the virtual instances and hypervisor, and the physical server resources.

As HATech scaled, they faced a challenge in managing and supporting a rapidly expanding pool of customers, especially those releasing changes to their software every few hours. Without an automated monitoring platform, they could not see into their customers’ infrastructure, and they were blind to potential problems. They needed a way to receive immediate alerts about any issues, and they needed real-time, detailed data to support rapid troubleshooting, even as customers’ infrastructure evolved day by day. They began a deep and thorough search for a monitoring platform that was fast, reliable, required no infrastructure management, offered flexibility to create custom add-ons, agents, and plug-ins, and was affordable.

SpringServe, a video ad server platform, was facing challenges with its self-hosted monitoring stack which could not correlate metrics between systems, making it difficult to identify and resolve issues before they directly impacted the customer experience. As SpringServe's infrastructure was becoming more dynamic and distributed to provide better service around the world, significant blind spots hampered those efforts. They could not track application performance across regions, nor could they correlate metrics between systems to uncover the source of issues. SpringServe needed a reliable, real-time monitoring solution that could keep pace with its auto-scaling infrastructure, allow them to adopt innovative technologies, and keep growing quickly—without sacrificing the speed or consistency their customers depend on.

CMD Solutions required visibility into cloud workloads and infrastructure so they could facilitate safe and reliable cloud migrations for their customers. They also needed to be able to discern between critical signals and false alarms in order to mitigate any performance or availability issues that might occur in their customers' dynamic environments. CMD must maintain a high-level view of all of their customers’ environments at once. But with all customers requiring high-touch service simultaneously, CMD needed tools and processes that would allow them to migrate and support customer workloads without engaging in time-consuming, manual work that could take attention away from critical system issues.

Zendesk was transitioning to a highly dynamic, container-based environment and needed a robust monitoring solution that integrated with AWS and Kubernetes. Their existing monitoring tools created silos between teams and required manual correlation of metrics, traces, and logs, which made it difficult to resolve issues. To keep up with their customers’ evolving needs, Zendesk’s developers need the freedom to build new features quickly. Historically, Zendesk had used a monolithic, on-premises architecture for its production workloads, while its nonproduction workloads ran on Amazon Web Services (AWS). This setup created a lot of friction for their developers and made it difficult to scale.

Devsisters, a leading mobile gaming company, needed visibility into the health of their applications to meet the demands of their rapidly expanding user base. Their existing tools added complexity that made it increasingly difficult to pinpoint user-facing issues. Additionally, the implementation and integration of these tools into their tech stack required a significant and continual time investment from the engineering team. As Devsisters’ engineering team set out to monitor and ensure the reliability of their cloud-native systems, they initially adopted a handful of open source tools for their perceived low cost. However, implementing and integrating these tools with their tech stack required a significant time investment from the engineering team, both upfront and continually. More importantly, Devsisters realized that these open source tools could not handle the scale and complexity of their modern environments.

PedidosYa, a member of the Delivery Hero group, faced a challenge when the company introduced free food vouchers for new users. Users were creating several accounts from different IP addresses to receive multiple vouchers, but this behavior was difficult to pinpoint and prevent at scale. The team’s threat detection workflow at the time involved manually creating firewall detection rules for every domain they operate, which was grueling, time-consuming, and required lots of maintenance. As fraudulent activity increased, it became impossible to create individual rules for every IP address that needed to be blocked. This process led to a month-long delay in detection, which gave the malicious actors enough time to achieve their goal.

Vidio, a leading video streaming service in Indonesia, needed a monitoring solution to ensure a smooth and latency-free experience for their users. The company required visibility into their dynamic cloud environment, which was crucial for maintaining application uptime and consistent high stream quality. The challenge was to find an intuitive platform that would not add extra overhead to its Engineering and DevOps teams. This was particularly important during live sports events, which can attract an audience of up to eight million viewers.

Fundbox sought to enhance its DevOps processes by boosting responsiveness to software issues and reducing time spent maintaining its many monitoring tools. The company wanted one holistic solution that could empower developers to quickly spot and fix issues without being weighed down by so many monitoring systems. The complexity of the Fundbox monitoring infrastructure made it hard for DevOps engineers to quickly spot and resolve issues in production. And a few of these individual monitoring tools required extensive DIY customizations and ongoing maintenance. All this extra overhead reduced the time available for engineers to perform core DevOps functions, such as updating Fundbox services.

Delivery Hero, a leading local delivery platform, experienced a sharp increase in application traffic due to the global pandemic. They leveraged Kubernetes to scale and maintain their containerized environment, but visibility gaps threatened their ability to handle the increased traffic. Their existing open source tools could only monitor one of their clusters at a time, creating critical blind spots during updates or new cluster additions. They also lacked visibility into their DNS services, which are used by Kubernetes for service discovery and communication. This lack of visibility made them vulnerable to potentially large-scale outages and slowed down the issue detection and resolution process.