General Looker administration
All your administration & self-hosting questions and content
- 451 Topics
- 1,199 Replies
Problem: All users are locked out of the instance either because:you enabled SAML/LDAP on your instance without an alternate account login setup, and you set those authentication methods with incorrect configurations you disabled SAML/LDAP while you are logged in to looker via SAML/LDAP without an alternate account login set up Solution: toggle those features OFF via code depending on two situations:If you know your client id/secret: run the custom codes below LDAP: https://github.com/lanlooker/Looker-Tutorials/blob/main/07_Update_LDAP.ipynb SAML: https://github.com/ryookuriki/Looker-Tutorials/blob/main/update_SAML.ipynb If you DON’T know your client id/secret: 1. Have DCL disable the feature for you via Looker Support 2. Obtain client id/secret from Admin > Users for your account 3. Have DCL enable the feature for you via Looker Support (This will most likely lock you out of your instance again 4. Run the code below to toggle the feature OFF LDAP: https://github.com/lanlooker/Loo
Hey, we are trying to upgrade our Customer/on-prem hosted looker instance version to latest release. And we are facing the below error while starting the looker on an instance.“The --force-gcm-encryption flag can only be used on a new Looker install”“--force-gcm-encryption flag was used but Legacy crypt canary exists” Does anyone faced this issue? May I know how to resolve this?
Our organization requires specifying server side encryption with all PutObject requests to S3 (see https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingServerSideEncryption.html).Does Looker provide any way to add additional headers to S3 file delivery? Specifically I need to specify:"s3:x-amz-server-side-encryption": "AES256"
I am trying to install a Looker Block from a Git URL, and I receive the following error during the last step, clicking “Install” after configuring the block:An unexpected problem occurred. Please try again. Below are some screenshots that illustrate the issue:
I’ve connected Looker to a MySQL instance and even added extra connection parameters like: characterEncoding=utf8characterSetResults=utf8 but for some reason, even in SQL Runner, the data is displayed like this:I added the above connection options as that’s how my DataGrip is configured and there the data is displayed correctly. Am I missing something?
Hello, we currently have a user who was initially able to log in and view the app on Android, but once exiting the app, is unable to get the app to load. Screenshots below. I have a couple questions, thanks for your help! Is this the channel for communicating potential issues with the app? Is this a known issue with Android?
Trying to combine hub & spoke (spoke project B imports hub project A) with multi-environment workflow to import spoke into production instance.
We would like to set up a multi-environment workflow for embedded analytics, with two Looker hosted instances: development and production. We also do internal business intelligence, and would like to reuse explores for internal and external embedded use. The external embedded versions of the explores should be the same as the internal versions, just with the addition of access_filters to support SSO embed. Thus, I thought we could do a hub & spoke layout to recycle the explore logic (where the spoke would refine the explores from the hub and add access_filters).I thought we could do this setup: Development environment (company_development.looker.com)hub project - defines explores, which are useful for both internal business intelligence and external embedded reporting. Used for internal BI in production mode of this environment. external_reporting_spoke_development project - remote imports hub project. Adds access_filters to explores. Used for development and testing of embedded
We are trying to troubleshoot an issue where a query is executed in Looker and shows up as ‘running’ in the query page yet it has not even been sent to redshift. The query in question has been identified by the history_id and it shows that it took 400 seconds to execute according to Looker’s system reports yet only 5 seconds to execute in Redshift (0 seconds queued). Is there a way to determine if a specific query (based on history_id) was queued by Looker - and if so, why was it queued? Also, why would it show up as ‘running’ in the queries page - is this a potential bug? From this article, it looks like these are some reasons that a query could be queued:Per-User Query Limit and TimeoutEach Looker user is allowed to run 15 queries simultaneously by default. Any extra queries are queued in Looker until one of the 15 running queries finishes. If they stay in queue for over 600 seconds, then Looker drops them from the queue.Scheduler Query Limit and TimeoutScheduled queries are run by t
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
I have a problem when I try to start Node 2 in a cluster, Node 1 starts fine, here is the error reported in two phases, Firstly when I start up there are many of these. Currently running 6.12.17, but was the same yesterday running 6.2.26. 2019-06-11 09:31:27.901 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 650 attempt(s) continuing to retry. 2019-06-11 09:46:28.367 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 660 attempt(s) continuing to retry. 2019-06-11 10:01:28.833 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 670 attempt(s) continuing to retry. 2019-06-11 10:16:29.409 +0000 [WARN|0082e|org.apache.activemq] :: Failed to connect to [tcp://172.31.15.112:61616, tcp://172.31.26.230:61616] after: 680 attempt(s) continuing to retry. 2019-06-11 10:31:29.9
The new left-hand nav is driving our entire team nuts.Accessing navigation – at all – requires a mouseclick instead of just mousing over to the permanent navigation bar Access menus like Develop used to just take a mouseover but now requires a full mouse clickThese changes are materially impeding our productivity.We'd really love to have the Looker Product team reconsider this design change and to add back the Legacy Feature until some changes are made.
Hi Good Lookers! I’m trying to follow the instructions provided in this article that describes how to set up two different Looker instances to use a single GitHub repository. I’ll refer to the first Looker instance as “Staging” and the second Looker instance as “Production”. Note that I’m self-hosting Git (using GitHub) and not using Looker’s git hosting service. Here’s what I’ve done and where I’m at so far:I configured “Staging” to use Pull Requests I created a webhook in GitHubI can now make changes in “Staging” and a Pull request is created in GitHub for approval. All good!Where I’m stuck is in configuring a release webhook to “Production”.Right now “Production” is a bare Looker instance with no projects. I want to create a new project that uses the same Git repository as “Staging”. I want changes to “Staging” to be reflected in “Production”. How do I configure this?I’ve circled in yellow the parts of this process (as described by the linked article) that confuse me.
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
Hi folks,We have groups of external users to whom we need to email Looker content. Those group memberships are managed in our own (non-Looker) configuration system and in some cases are managed by our clients directly.We could easily sync those user groups to match corresponding groups in Looker, but one key gap remains: there is no option in Looker to add a Looker group as a recipient of a scheduled dashboard (i.e. email report).This is critical for us and seems like a very natural feature, but the Looker team needs more clients asking for this in order to prioritize it.Please reply here if you would use this feature. (If you’re willing, asking your account team to pass along your request to Looker’s Product team would be very helpful.)Thanks!PeterP.S. An email distribution list won’t work for us here because our group definitions affect other parts of our application (and we don’t want one user to unsubscribe the whole group). Currently, we use the Looker API to send our own email, b
After upgrading Version 21.16.43 to 21.20.32, scheduled jobs are hanging while generating PDF.I do have some instances of: “Render error: Script timed out” in our logs. I have tried the suggestions here with no success. Is there anyone who can suggestions as to how to debug this further? I can download the PDF normally, just not via the scheduled_job.
I wanted to provide feedback about the decision to end the email communication of deployments and release notes and moving this into Looker itself.As a customer using Looker as an embedded BI tool, we just aren’t in Looker every week, sometimes every month. If a breaking change is released we need as much notification as possible to address it quickly for our customers. It was great to get that release email, review the changes and adjust as necessary. Now I’m concerned we’ll have to create a new process that requires proactively going into Looker every week(?) and checking for release notes and deployment information.Does anyone else feel this is a step backward?Anyone replace this with some kind of automation?Thanks!
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.