General Looker administration
All your administration & self-hosting questions and content
- 451 Topics
- 1,199 Replies
Hi Everyone, I’m curious to find out if looker hosted installs have an SLA yet and if there’s a dedicated status page or RSS feed of outages in the Looker infrastructure? Knowing when looker is having an outage is important to monitor in an application that is critical to the business. Thanks
The Chromium renderer is the process on the Looker server responsible for creating PDFs and PNGs of dashboards and Looks. Errors from Chromium or image render jobs in general can tend to be a bit generic. This page provides an overview of the most common Chromium image rendering errors and how to troubleshoot them. These errors most commonly occur with customer hosted Instances, as Chromium is automatically installed and updated on Looker hosted instances. First, Make sure Chromium is installed The first step to troubleshooting any image rendering error is to confirm that Chromium is installed correctly, and that Looker can access it by running the following commands:chromium --versionThis should return something like:Chromium 70.0.3538.77 Built on Ubuntu , running on Ubuntu 16.04Next, make sure Chromium is in the proper place, which is /usr/bin/chromium: which chromiumThe output should be:/usr/bin/chromiumRunning these two commands confirms that Chromium is installed correctly on a
Looker Actions - Google Cloud Storage Looker is launching a Google Cloud Storage action, allowing customers to send data to Google Cloud Storage from within Looker. This action will allow Looker customers ti send Looker data to Google Cloud Storage on a one-off or scheduled basis. Enable the Google Cloud Storage Action Note: Your Looker instance must be on Looker 5.6+. Customer-hosted instances may be unable to enable actions from the Looker Action Hub, especially actions that support streamed results or that use OAuth, if the customer-hosted Looker instance does not fulfill these requirements. See the Sharing Data Through an Action Hub documentation page for suggested solutions to this potential issue. To enable the action in Looker, go to your Admin panel and the Actions Tab under the Platform header [your-instance.looker.com/admin/actions]. (Admin > Platform > Actions) Select “Enable” on the Action you would like to enable. In your Google Cloud console [https://consol
If you are connecting to a git repository via HTTPS and you have Two-Factor Authentication enabled on your git repository account, you will need to use an access key as your password, rather than your account password with username. To set up these access keys: In GitHub: 1. In the upper-right corner of any page, click your profile photo, then click Settings. In the left sidebar, click Developer settings. In the left sidebar, click Personal access tokens. Click Generate new token. Give your token a name. Select repo permissions. Click Generate token. Click to copy the token to your clipboard. For security reasons, after you navigate off the page, you will not be able to see the token again. Use this token instead of your password, with your username, to connect to your repository in Looker. In GitLab 1. In the upper-right corner of any page, click your profile photo, then click Settings. In the left sidebar, click Access Tokens Give your token a name Select api permissions.
Use this post together with the Looker Document Setting Up Version Control to configure your version control with GitLab. Refer to the instructions in the Setting Up Version Control document. You can create a new repository in GitLab by clicking the + icon in the upper right corner of any page and selecting “New Project,” then follow these instructions: https://docs.gitlab.com/ee/gitlab-basics/create-project.html Get the SSH URL for your GitLab repo. The format should look like this: firstname.lastname@example.org:<organization-name>/<repository-name>.git ￼ You can see the SSH URL by clicking on the project’s Details tab. Refer to Step 3 in the Setting Up Version Control document Looker will detect your Git provider and display a deploy key for your repo. (If Looker does not successfully detect your Git provider, it will ask you to choose from a dropdown.) Select the entire Deploy Key and copy it to your clipboard, then click the link under “Add the SSH Key” to visit the SSH K
Hello!I’ve been getting persistent errors at seemingly random occurences when I try to create a new dashboard and edit a tile. After clicking save dashboard, the error pops up as a red banner as ‘Uh oh. Your save failed’. I would have to close browser and try again.Any thoughts on why this may occur? What would prompt this error message? Is it a connectivity issue to an API of some sort?
Author: Jonathon Miller-Girvetz @jonathon The "Looker is having trouble connecting to your database" error can occur when you least expect it. For example, while running an Explore - BAM! There it is: Has this ever happened to you? Read on to learn about what causes this error, and how to resolve it. Why did this error happen?Looker's connection pool timeout is the only known cause of the "Looker is having trouble connecting to your database" error.Basically, the following occurred:Looker tried to send a new query to a database. This query could have been triggered by a dashboard, Look, Explore, SQL Runner, etc. Looker noticed that it had already sent a number of unreturned queries to the database greater than or equal to the Max Connections setting in a connection’s settings page in the Admin panel. Looker queued the query to give the database a chance to complete the queries that are already running. It's really important that Looker does this - by doing so, Looker protects datab
Is anyone running an on-premise install of Looker using Docker? We currently run our on-premise Looker instances (prod & staging) directly on AWS EC2 instances, but for a variety of reasons we are considering switching to using Docker. I imagine the main issues in doing this would be: Need to use external DB for Looker (we already use RDS MySQL for this) Cached results wouldn’t persist between container restarts if using ephemeral storage Maybe any license issues if running on different container instances between restarts? Surprisingly, I haven’t been able to find any reference to doing this when googling and searching these forums. Is anyone doing this? For the Looker folks, any info or concerns about running this way? Thanks! -Joe
Has anyone had success using Office 365 for SMTP with Looker? I get this error when attempting to send a test email: Failed to send mail: 504 5.7.4 Unrecognized authentication type I’m selected the check box for SSL/TLS. I did note that the setting I’ve had to use with another tool is START TLS. I’m not clear on whether that variant should be handled by the SSL/TLS option.
This shouldn’t be a hard one, but I’m not able to figure it out as a new Looker user. I have an SQL query to pull the following data: |Date|Company|Share Price| That part is good and was easy. I want to draw a chart that has the following features: x-axis: date y-axis: share price two series line graphs, one for each of the companies that I’m tracking. Theoretically, I should be able to Pivot on name, but I can’t figure out how to get the share price value into those company columns.
How to embed Looker into an IFRAME having a domain different from the domain of the embedding application
I am researching how Looker can be embedded as an IFrame using sso on a domain which is different from the domain of the embedding application. Can any one point me to the right approach or resource on how to achieve this?
Let’s talk about the Data Dictionary! It would be good to gather feedback and requests in one place. I think it would be great addition in the future. My humble requests and observations: I really like the UI. It’s clean and yet has a lot of information. Would prefer the list of fields to be more compact (in general I use 80% zoom anywhere in Looker) Optional display of fields from JOINs. Otherwise each explore gets big with repetitive metrics. I have two explores that are joined to everything. No need to show their fields on each page, they have their own page. Showing the explore fields first then the JOINs’. If it happens that my explore starts with N but join starts with A, the join fields will be first. I think the order should go with the importance and then alphabet. If I have a join in each explore that starts with A, then it will look like it’s the same page everywhere (until people start scrolling a lot). Ability to add descriptions that only live in Data Dictionary n
I am trying to do some maintenance on our Looker install and have found a whole bunch of views that someone created but I am pretty sure are not being used anywhere. But thus far I have not found a reliable way of telling if specific views and dimensions are in fact being used in Looks anywhere. The closest that I can come up with is going to dev mode, removing something and then using the content validator to see if it comes up somewhere. It would be great of there was a “Find Uses Of…” function for Views/Dimensions/Measures.
What does `Error: Your scheduled job failed because the results stored in cache were expired or invalid. To resolve, please retry your schedule or wait until the next scheduled job.` mean on my failed schedule delivery?
TL:DR: The cached results for the queries expired before Looker was able to send out the results. This commonly occurs when lots of schedules are set to run at the same time, are particularly large deliveries, or to more complex endpoints, like Google Sheets. Staggering the schedules over a longer time period should help. To understand what it going on with this error it will be useful to look into the entire schedule delivery process, which is more comprehensively outlined in this Community post but key points highlighted here. All schedule jobs that run will go through 4 phases, with 2 of them having concurrency limits: Enqueue for execution - waiting in line for query executing for the schedule Execute - actually running the queries against the database or verifying valid cache for the queries which is default limited to 10 concurrent threads. Enqueue for delivery - waiting in line for the cached results from the Execute stage to be sent off Delivery - actually sending this
When downloading queries, some queries could require large amounts of memory. Old Behavior When downloading all results for some types of queries, the amount of memory required could cause performance issues, even crashing an instance. The All Results option is disabled for users with download_with_limit permissions but other users could download all results even for queries that have memory-intensive characteristics. New Behavior Starting in Looker 4.14, you can prevent these queries by turning off the Allow unlimited downloads that might crash Looker legacy feature. When the legacy feature is off, the All Results option is disabled for queries returning more than 50,000 rows in situations where the rows need to be stored in memory. This includes queries returning more than 50,000 rows with one of these memory-intensive characteristics: involving row totals or table calculations using percent_of_total, percent_of_previous, or running_total measure types getting data from a database
Our entire platform runs on AWS Linux. Amazon does not have chromium in its repos: # yum list | grep -i chromium Is there a recommended way to install chomium on AWS Linux for Looker? I see the post here: Chromium 64+ must be installed Dashboards & Visualizations Following the instructions here https://docs.looker.com/setup-and-management/on-prem-install/on-prem-labs; “Installing Software to Run Looker Labs Features” I have installed both PhantomJS and Chromium. However when I goto the Labs section to enable the Enhanced Rendering feature I get the following message. [image] In the terminal when I check the installed version “chromium --version” I get the following “Chromium 69.0.3497.81 Built on Ubuntu , running on Ubuntu 18.04” Any help would be ap… And tried running this command (which works, but doesn’t install anything): sudo yum localinstall http://install.linux.ncsu.edu/pub/yum/itecs/public/chromium/rhel7/noarch/chromium-release-2.2-1.no
The PDT regenerator process is responsible for checking SQL triggers and rebuilding derived tables that are persisted with a SQL trigger which is defined either a datagroup or sql_trigger_value.The regenerator is considered “hung” when: It reports that it is executing SQL for a PDT build or trigger check, and that SQL is not executing on the database. The regenerator process has not begun after the previous regenerator process has completed within the timeframe dictated by the PDT And Datagroup Maintenance Schedule connection setting. Why do hung regenerators occur?The source of a hung regenerator can be difficult to track down, as it typically involves the network or database side of the process interrupting PDT regeneration. We have seen a number of reports of hung regenerators coinciding with Redshift database maintenance, including a mass maintenance that Redshift performed. Make sure to confirm this is not the case before moving forward with troubleshooting.You can use the wor
Already have an account? Login
Login to the community
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.