Elasticsearch vs. Google Analytics vs. Grafana

Elasticsearch is a really scalable solution that can fit a lot of needs, but the bigger and/or those needs become, the more understanding & infrastructure you will need for your instance to be running correctly. Elasticsearch is not problem-free - you can get yourself in a lot of trouble if you are not following good practices and/or if are not managing the cluster correctly. Licensing is a big decision point here as Elasticsearch is a middleware component - be sure to read the licensing agreement of the version you want to try before you commit to it. Same goes for long-term support - be sure to keep yourself in the know for this aspect you may end up stuck with an unpatched version for years.

Incentivized

Google Analytics is particularly well suited for tracking and analyzing customer behavior on a grocery e-commerce platform. It provides a wealth of information about customer behavior, including what products are most popular, what pages are visited the most, and where customers are coming from. This information can help the platform optimize its website for better customer engagement and conversion rates. However, Google Analytics may not be the best tool for more advanced, granular analysis of customer behavior, such as tracking individual customer journeys or understanding customer motivations. In these cases, it may be more appropriate to use additional tools or solutions that provide deeper insights into customer behavior.

Just about any organization with more than one server and more than one cluster as it scales very well. Configuration of the application takes time and finesse to fine tune to where the balance of load time and getting data quickly meets. The plugins add load time but fine tuning for the application to meet demand needs nailed down at implementation

Incentivized

• As I mentioned before, Elasticsearch's flexible data model is unparalleled. You can nest fields as deeply as you want, have as many fields as you want, but whatever you want in those fields (as long as it stays the same type), and all of it will be searchable and you don't need to even declare a schema beforehand!
• Elastic, the company behind Elasticsearch, is super strong financially and they have a great team of devs and product managers working on Elasticsearch. When I first started using ES 3 years ago, I was 90% impressed and knew it would be a good fit. 3 years later, I am 200% impressed and blown away by how far it has come and gotten even better. If there are features that are missing or you don't think it's fast enough right now, I bet it'll be suitable next year because the team behind it is so dang fast!
• Elasticsearch is really, really stable. It takes a lot to bring down a cluster. It's self-balancing algorithms, leader-election system, self-healing properties are state of the art. We've never seen network failures or hard-drive corruption or CPU bugs bring down an ES cluster.

Incentivized

• Multiple reports to see website use and behavior
• Allows you to customize reports with days, weeks, months, and years
• You can build out a dashboard to easily view stats from multiple websites in one place
• You can share analytics reports via the dashboard, automatically emailed PDFs or in other formats

Incentivized

• Alerting through many different medium as Slack, Email, Webhook etc
• Beautiful and unlimited number of dashboards to view your metrics and tweak them as you please
• Log aggregation and powerful Logql to filter and view your logs
• Microservices monitoring
• Large number of plugins and data sources to collect your metrics from almost anywhere

Incentivized

• Joining data requires duplicate de-normalized documents that make parent child relationships. It is hard and requires a lot of synchronizations
• Tracking errors in the data in the logs can be hard, and sometimes recurring errors blow up the error logs
• Schema changes require complete reindexing of an index

Incentivized

• Data sampling is somewhat inaccurate on the free tier - this is addressed in premium but is expensive.
• Some of the UI is very similar in naming when presenting different data, some in-situ information might be useful.
• Gotchas around filtering and data validation.
• Implementation can be tricky, it can take a lot of time and expertise to get a full, accurate picture of your metrics.

Incentivized

• There are some settings which we can't configure from UI (Web Console).
• We've open[ed] up configuration files in command line text editors and manually do the settings e.g. LDAP/SSO configuration.
• In terms of visualization, it's best, but it doesn't support log analysis otherwise it could destroy business of all other visualization tools.

We're pretty heavily invested in ElasticSearch at this point, and there aren't any obvious negatives that would make us reconsider this decision.

Incentivized

We will continue to use Google Analytics for several reasons. It is free, which is a huge selling point. It houses all of our ecommerce stores' data, and though it can't account for refunds or fraud orders, gives us and our clients directional, real time information on individual and group store performance.

Incentivized

To get started with Elasticsearch, you don't have to get very involved in configuring what really is an incredibly complex system under the hood. You simply install the package, run the service, and you're immediately able to begin using it. You don't need to learn any sort of query language to add data to Elasticsearch or perform some basic searching. If you're used to any sort of RESTful API, getting started with Elasticsearch is a breeze. If you've never interacted with a RESTful API directly, the journey may be a little more bumpy. Overall, though, it's incredibly simple to use for what it's doing under the covers.

Incentivized

Google Analytics provides a wealth of data, down to minute levels. That is it's greatest detriment: find the right information when you need it can be a cumbersome task. You are able to create shortcuts, however, so it can mitigate some of this problem. Google is continually refining Analytics, so I do not doubt there will be improvements

It is infinitely flexible. If you can imagine it, Grafana can almost certainly do it. Usability may be in the eye of the beholder however, as there is time needed to curate the experience and get the dashboards customized to how it makes sense to you. I know one thing they are working on are more templates, based on data sources

Incentivized

We all know Google is at top when it comes to availability. We have never faced any such instances where I can suggest otherwise. All you need is a Google account, a device and internet connection to use this super powerful tool for reporting and visualising your site data, traffic, events, etc. that too in real time.

This has been a catalyst for improving our site's traffic handling capabilities. We were able to identify exit% from our sites through it and we used recommendations to handle and implement the same in our sites. We have been increasing the usage of Google Analytics in our sites and never had any performance related issues if we used Analytics

We've only used it as an opensource tooling. We did not purchase any additional support to roll out the elasticsearch software. When rolling out the application on our platform we've used the documentation which was available online. During our test phases we did not experience any bugs or issues so we did not rely on support at all.

Incentivized

The Google reps respond very quickly. However, sometimes they can overly call you to set up an apportionment. I'm very proficient and sometimes when I talk to reps, they give beginner tutorials and insights that are a waste of time. I wish Google would understand my level of expertise and assign me to a rep (long-term) that doesn't have to walk me through the basics.

Incentivized

love the product and training they provide for businesses of all sizes. The following list of links will help you get started with Google Analytics from setup to understanding what data is being presented by Google Analytics.

1. How to Use Google Analytics for Beginners – Mahalo’s how-to guide for beginners.
2. A beginner’s guide to Google Analytics – A free eBook walking you through Google Analytics from setup to understanding what data is being presented.
3. Getting to Know Your Google Analytics Dashboard – The title says it all! This is a brief post with one goal: to introduce you to the Google Analytics dashboard.
4. Google Analytics for Beginners: How to Make the Most of Your Traffic Reports– This guide doesn’t cover setup, but it does a great job of helping you to better understand the data being presented.
5. Google Analytics Video Tutorial 1: Setup – A video presentation that walks you through Google Analytics setup.
6. Google Analytics Video Tutorial 2: Essential Stats – A video presentation that introduces you to some of the most important data being presented in Google Analytics.

Do not mix data and master roles. Dedicate at least 3 nodes just for Master

Incentivized

I think my biggest take away from the Google Analytics implementation was that there needs to be a clear understanding of what you want to achieve and how you want to achieve it before you start. Originally the analytics were added to track visitors, but as we became more savvy with the product, we began adding more and more functionality, and defining guidelines as we went along. While not detrimental to our success, this lack of an overarching goal resulted in some minor setbacks in implementation and the collection of some messy data that is unusable.

As far as we are concerned, Elasticsearch is the gold standard and we have barely evaluated any alternatives. You could consider it an alternative to a relational or NoSQL database, so in cases where those suffice, you don't need Elasticsearch. But if you want powerful text-based search capabilities across large data sets, Elasticsearch is the way to go.

Incentivized

I have not used Adobe Analytics as much, but I know they offer something called customer journey analytics, which we are evaluating now. I have used Semrush, and I find them much better than Google Analytics. I feel a fairly nontechnical person could learn Semrush in about a month. They also offer features like competitive analysis (on content, keywords, traffic, etc.), which is very useful. If you have to choose one among Semrush and Google Analytics, I would say go for Semrush.

Incentivized

Grafana blows Nagios out of the water when it comes to customization. The ability to feed almost any data source makes it very versatile and the cost is great.

Incentivized

Google Analytics is currently handling the reporting and tracking of near about 80 sites in our project. And I am not talking about the sites from different projects. They may have way more accounts than that. Never ever felt a performance issue from Google's end while generating or customising reports or tracking custom events or creating custom dimensions

• We have had great luck with implementing Elasticsearch for our search and analytics use cases.
• While the operational burden is not minimal, operating a cluster of servers, using a custom query language, writing Elasticsearch-specific bulk insert code, the performance and the relative operational ease of Elasticsearch are unparalleled.
• We've easily saved hundreds of thousands of dollars implementing Elasticsearch vs. RDBMS vs. other no-SQL solutions for our specific set of problems.

Incentivized

• It has helped us gain understanding of what is going on on our website.
• It has helped us determine areas that need fixing (i.e. pages with extremely high bounce rates may need to be redone).
• It has helped us understand our biggest avenues for bringing traffic to the website and business in general.
• It has helped guide our website redesign.

Incentivized

• Grafana has replaced many higher priced tools
• The integrations are seemless with multiple backends
• Combining graphs and dashboards from multiple data sources is a game changer

Incentivized