Fantastic for detailed data, especially for tracking user journeys from social media onto the website, for example. Great for use across multiple people in teams, even where only one or two people have a full understanding of the tool, as it is user-friendly once set up. Not hugely appropriate for presenting in and of itself, best as a source of raw data versus a tool to convey findings.
This program works from the roots of the problem and creates a professional matrix for each of its users. This will give them more skills and resources to carry out tasks and reduce the difficulties of operating each of the processes of my work, as well as being An ally for the manipulation and operability of all your master data; Prometheus is very easy to recommend since it is a program that fulfills its mission.
Looker Studio helps us track error metrics in one place, making us more efficient as a team because we don’t have to switch between systems to gather data and then create a separate report.
Since our SQL data is pretty messy, it helps us with clean data reporting by visualising spikes in errors.
It also improves our communication with management, who are non-technical, by providing an easy-to-understand dashboard report.
Customer Service: since this is an open-source tool, customer service is not that great. Generally, you get all answers to your problems in online forums, but in case you got stuck, nobody will assist you in a channelised manner. You will have to find the way out on your own, and it may become frustrating at times.
More metrics for dashboards shall be added per the application being monitored. Standards metrics will work in most cases but may not in specific applications. Therefore, customised metrics shall be created for some of the industry-standard niche applications.
It is the simplest and least expensive way for us to automate our reporting at this time. I like the ability to customize literally everything about each report, and the ability to send out reports automatically in emails. The only issue we have been having recently is a technical glitch in the automatic email report. Sadly, there is almost no support for this tool from Google, but is also free, so that is important to take into consideration
Looker Studio is easy to use, and it offers a sufficient variety of predefined visualizations to choose from. It's easy for us, and anyone can set up basic reporting without extensive data visualization skills. The interface layout is easy to understand, and it doesn't take long to get used to.
It is usable and one can learn if few people in the team are already using it. It can be difficult to understand at the beginning because of non intuitive UI and syntax of the rules. So, I've gone for 7 points as there is some room for improvement in user interface and rules syntax.
I give it a lower support rating because it seems like our Dev team hasn't gotten the support they need to set up our database to connect. Seems like we hit a roadblock and the project got put on pause for dev. That sucks for me because it is harder to get the dev team to focus on it if they don't get the help they need to set it up.
The free version of Looker Studio is still better than the leading enterprise-embedded BI tools, despite its weaknesses. The leading embedded BI platforms have terrible visualizations that can be spotted a mile away. They are also primarily locked to a grid, making it very hard to fully customize. The price point is also a major deterrent, since users end up paying for lots of features they might never use. Looker Studio has weaknesses on the blending and modeling side, but we've been able to get by via connection to GBQ and transformation done in dbt.
Highly customized pricing plans to choose from. Lower pricing for the same features compared to competitors. Easy to reach the support team, which provided detailed documentation and helped set up the Prometheus. Monitoring metrics gets very easy after the integration with Grafana. It also has a sophisticated alert setting mechanism to ensure we don't miss anything critical.
The ROI mentioned during the purchase has not been achieved, however this could be due to lack of data from our side. 2 years of implementation is too early to calculate and confirm the ROI.
