With various open source platforms on the market, engineers have to make smart and cost-effective choices for their teams in order to scale. Elastic Cloud, and…
Google Cloud Operations, formerly known as Stackdriver, is relatively new to the observability space. That being said, its position in the GCP ecosystem makes the platform a serious contender.
Let’s explore some of the key ways in which Google Cloud Operations differs from Coralogix, a strong full-stack observability platform and leader in providing in-stream log analysis for logs, metrics, tracing and security data.
Both Coralogix and GCP offer support for logs, metrics and traces. Both solutions also support direct integrations into OpenTelemetry, enabling customers to integrate in an open-source fashion, and avoid vendor lock-in.
There is a great deal of difference in alerting with Coralogix vs Google Cloud Operations.
While GCP supports alerting on logs to detect specific fields that appear in logs, the platform is limited to only this type of alerting capability. Notably, Google Cloud Operations do not support alerts that involve counting a set of logs that match a given query.
In comparison, Coralogix offers six different types of alerts—from simple log count to ratio and time relative alerts—with log alerting that is one of the most sophisticated options on the market. Our platform enables highly sophisticated insight generation.
Coralogix also supports the “more than usual” and “less than usual” dynamic alert conditions, driven by a machine-learning algorithm to detect anomalous data flow patterns in customer data. Coralogix alerts enable the detection of “unknown-unknowns” and act as a safety blanket to catch issues that may otherwise go undetected.
Google only supports alerting on traces in specific circumstances, like detecting changes in ingest rate. Thus limits the ability of the customer to detect important changes in the latency and performance of their system.
Coralogix supports alerting on traces and allows for alerts to track down specific interactions between applications and even individual endpoints. Therefore, Coralogix alerts give a voice to the wealth of information hidden within traces that often go unnoticed.
Google Cloud Operations separates data types out into different services, and encourages customers to access different values in different interfaces. If they wish to overcome this limitation, they have to make an up-front effort to build dashboards at cost.
Coralogix, on the other hand, seamlessly blends data together in a single, rapid troubleshooting experience, which reduce Mean Time To Diagnosis (MTTD) and accelerates recovery.
Coralogix alerting has unique features like Coralogix Flow Alerts, which allow users to orchestrate their logs, metrics, traces, and security data into a single alert that tracks multiple events over time. Using Flow Alerts, customers can track the change in their system.
Google Cloud has machine learning driven anomaly detection in some of its services, but this is not a configurable part of the platform. On the other hand, Coralogix supports anomaly detection out of the box, with dynamic alerting.
Coralogix Loggregation is a unique feature in the Coralogix toolkit. Loggregation will automatically cluster similar logs together, to form a “template.” This functionality allows users to understand which logs are noisiest and accounting for the most errors and more.
Google Cloud does not offer a competitive alternative to this feature, and suffers from the same problems that traditional systems do when dealing with large volumes of data.
Google Cloud does offer a basic archiving solution, but it doesn’t have much functionality around it. Conversely, all Coralogix customers, regardless of ingestion amounts, can remotely archive their data into cloud object storage.
Since Coralogix does not tier its solution, customers who ingest their data into the platform gain immediate access to every single feature. With the Coralogix platform, you can also perform remote queries in seconds on archived, unindexed data.
Google Cloud does not offer this feature, and instead relies on its customers to perform the necessary engineering work to join together Amazon Athena, AWS S3 and more. All of this comes at an added cost.
Coralogix users start by indexing the majority of their data, but over time, they tend to transfer more data to the archive because data can be queried in seconds, at no extra cost. This functionality means customers can store the majority of their data in S3, and pay at most $0.004 / GB for storage.
Coupled with the Compliance ingest costs in Coralogix, $0.17 / GB, the GB cost for ingest and storage is $0.174 / GB for the first month. By contrast, Google Cloud advises customers to delete unused resources to save cost. While deleting is a standard practice across all tools, it is an indication of how little automated support there is for lowering monthly operational cost for observability data.
Coralogix doesn’t charge by cloud resources, but by ingestion volume. More than that, Coralogix allows customers to assign use cases to traces and logs, which drive instant cost savings via the TCO Optimizer. These decisions are flexible and reversible, and entirely risk free.
Another typical cost optimization strategy is to convert more expensive data types, like logs and traces, into metrics that can be retained for a long period of time without incurring additional cost.
Google Cloud supports log-based metrics, which enables customers to generate metric data from information available in their logs. Coralogix also supports this functionality, however with one key distinction. Coralogix Logs2Metrics do not cost anything extra. Google Cloud log-based metrics are considered “chargeable metrics” and come at an additional cost.
Google Cloud does not support converting Traces into metrics at all. Coralogix, on the other hand, allows customers to convert all of their traces into metrics that can be retained for as long as they like (default of 1 year), for a fraction of the cost.
The Coralogix pricing model is based entirely on GB ingested with no solution tiering or extra costs for features, making it easy for new customers to predict their costs. In comparison, the Google Cloud offering is based on a different price per service and data type, meaning it’s going to be very difficult to work out precisely how much you will spend.
Google Cloud support for outages and incidents comes in three tiers. Standard, enhanced and premium.
By contrast, Coralogix offers all customers a median 30-second response time, an SLA measured in minutes, and 24/7 support. Coralogix also offers a median resolution time of 43 minutes. It does all of this at no extra cost. The closest comparable response times between Google Cloud and Coralogix is their Premium support package, representing a huge $12,500 / month saving.
Google was the original author of Kubernetes, so their in-house Kubernetes monitoring is great, although it only offers the basic assessment of a cluster, like the number of nodes or amount of pods.
Coralogix has pre-built dashboards for Kubernetes Monitoring, Serverless monitoring and more, while also supporting open source dashboarding solutions like Grafana. Coralogix also provides a custom dashboarding solution for Coralogix users. These dashboards help with everything from resilience to cost-optimization use cases.
The platform’s reuse of open source dashboards, like JSON definitions for Grafana, and the time-to-value of premade dashboards makes its offerings the best of both worlds, while charging absolutely nothing extra for their use.
Let’s define a simple use case, to highlight the difference in cost between Google Cloud and Coralogix. Let’s say we have a customer who ingests 1TB each of logs, metrics and traces with a one month retention. How much will they pay in that one month?
According to the Google Cloud calculator, it will cost them roughly $694 to ingest and hold onto that data for a single month. However, this cost does not factor in support, along with any of the additional costs associated with using the Google Cloud platform.
Let’s be generous and assume no additional costs, but we are forced to include the cost of their Premium Support, because this is the closest product that Google Cloud offers to the Coralogix support model that comes as standard. This brings their total costs to $13,194.
Coralogix does not charge anything extra for support or feature usage. The only cost a customer pays is for the data they use, and nothing more. This means the monthly cost for 1GB of Logs, metrics & traces comes to $1,405. This comes with full support and access to every feature in the Coralogix platform, at no extra cost.
While Google Cloud Operations enjoys tight integrations into all major Google Cloud services, its poor user experience, lack of feature depth, missing archive features, complex pricing model and lack of effective cost-optimization means it falls behind when compared to the features available in the Coralogix platform.