Looker Connect Training
Help Center
Documentation
Community
Cloud Certifications
Can anyone at Looker confirm and comment on this thread?https://www.reddit.com/r/Looker/comments/t5jpwk/google_cloud_just_laid_off_the_entirety_of/If confirmed, I’m deeply concerned. Our company has been a long time Looker user. We have a monolithic implementation. One of the reasons we have stuck with Looker is their extremely passionate DCL: Iqbal, Ryan, Sasha, Olga, and many more.That stated, we currently have ~15 unresolved Looker bugs. The current staff working on them seem to have no idea what they are doing. They keep stating, “I’m checking with a colleague” and asking, “Can I follow up with you in email?” The emails never come.Yesterday, I spent 4.5 hours on chat trying to get answer to unexpected permissions behavior! I’m an engineer, not Looker’s QA department. I’ve my own work to complete! Google, your product is only as good as your people--and if the plan is to start shopping for staff at the Dollar Store, then I’m advising our company to keep an eye open for other an
Hello wonderful Looker people, Is there anyone else out there who is self-hosting their Looker instances and willing to share best-practices, horror stories, or anything else regarding the challenges of self-hosting? Remember, this is for posterity. I’ll kick it off. Right now I’m reviewing our scalability. We repackage Looker into our final product and we have quadrupled our customer base in the last 2 years. We are starting to run into performance issues. Before I share our current dilemma, it is important to note I’m a data analyst put in charge of taking care of our Looker nodes, not a proper devops person. And Looker staff, feel free to correct me I get this wrong (please, it would help me learn). The current struggle I’m working through is getting more CPUs per node. Currently, we have 4 nodes each with 8 CPUs. It seems when a customer creates a dashboard with many tiles (25+) and schedules it to be rendered, all of the rendering jobs get assigned to the same node. So we
We self-host Looker (“on-prem”) and have encountered several issues where Looker’s performance degraded into 50s response times per page load. We eventually identified the problem as being the bandwidth between the databases and our Looker instance. It was 2gbps and we needed around 15gbps.Given we white-label Looker, our our company has decided to use the load time of our primary Explore as a proxy for our customer’s UX. In such, I’ve written some Python to load the Explore on repeat, collecting load times and saving them to a database.This code does the following:Opens your Looker instance’s login page. Logs in. Enters OTP (2FA) code Starts a timer, loads your main Explore, waits until the “Run” button is ready, stops the timer. Saves the load times to a MySQL / MariaDB DB. Shuts down the browser session.Python script#!/usr/bin/env python3# -*- coding: utf-8 -*-"""Created on Fri Nov 20 09:48:54 2020@author: C. Thomas Brittain"""##################### Libraries####################impor
I’ve recently been working on moving our custom developers’ tools to an app in Looker using the Looker Extension Framework. As I’m building the layout, I’ve noticed a lot of the Looker Components are marked as “Coming Soon.” Do we know when? I’m trying to decide whether to begin using material-ui, or wait for the Looker components needed. Kind regards, –Thomas ps. What category should Looker Extension framework questions go under? And what tag is most appropriate to identify it?
Why do you hate us so much? Fitt’s Law and UXps. Yes, I realize I forgot a “T,” but Looker forums won’t let me correct a typo in the title. Why, why do you hate us?
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
