Add Looker-on Dropdown with airSlate SignNow

Add looker-on dropdown

all right so who are we I'm Sondra Roscoe I'm a Senior Product Manager at looker and I work with the administration team so the administration team is the team of engineers myself as a product manager and a designer and we are focused on building out features for you guys so we're focused on the looker administrator and making sure that you guys have all the features that you need to configure looker to make sure it's running smoothly on a daily basis and kind of keep the lights on and I'm Rachel Johnson I am a technical support engineer over on our DCL team the department of customer love a lot of you are probably pretty familiar with us we're the faces on the other side of the chat window and I am one of our authentication subject-matter experts and just to give a quick overview of what we're gonna go over today we will start with the home base of every looker administrator the admin console go over a couple fun features move into various authentication methods and finally end with a looker going over some monitoring and other reports all right so the liquor admin console I'm sure all of you are super familiar with it it's the home base of every liquor administrator and provides any and all configuration options that you might need there's over 20 different pages that can be used to set up various configurations customizations or other settings and this helps you keep in touch with making sure you're luckier instance is exactly how you need it to be in this talk like Sondra mentioned we're really just scratching the surface there's tons and tons of information there so be sure to click around afterward explore and you can ask us or any of the DCL members in the back of the hall any questions that might come up so our first tip is an important one to make sure that you're providing a technical contact this is found on the general settings page right there for you and the technical contact is super important since it's basically our lookers main line into your company and their instance this means that any of the emails in the technical contact area are people that will be receiving release notes including exciting news about upcoming features or any critical things that might happen and just making sure that you can receive any email that pertains to your liquor instance one quick tip is to include a group email or alias within that list this is especially helpful if any admin is to leave your organization there still is someone receiving these communications from liquor and so you're not completely cut off the other fun tip in the general settings page is adding a custom color palette looker comes with a couple of different pre-built color palettes that can be used and they're great but they might not be your branding if you want your reports to stand out to match your other marketing materials and just maybe your company colors are very seriously your favorite colors and you need them everywhere this is the way to do it as you can see here over on one side we have the blue green grey color theme this is the looker default color palette it's great but if I was say a breast cancer awareness organization it's not really my branding so instead I create this pink themed color palette and now all of my dashboards are matching exactly with the think pink idea that a breast cancer organization wouldn't want to have and for authentication as we all know data security is super super important we don't need any users any users accessing data that we don't really want them seeing so that leads us to authentication and making sure that everything's secure and exactly the way we want it to be in terms of security the first and simplest way to make sure that no users are hacking into your system or anything like that is to enforce secure and strict password requirements the requirements in looker can be customized which means if your security team has really strict and specific ideas of what they want a password to look like you can make sure that your look your passwords also match those requirements this means special characters maybe numbers or the specific number of characters that need to be included in a password length are all customizable and can match your organization the other portion of data security includes two-factor authentication this means that a user is not only entering just their password to gain access to the instance they are also having to provide a one-time code that is generated when they attempt to login and this gives another factor of making sure that we know the user truly is who they say they are before they gain access to the instance data security thumbs up all around there the another option when it comes to authentication is using an external authentication method currently looker supports four different methods including Google OAuth sam'l LDAP and open ID connect any of these four can be configured from the admin panel and if you ever are attempting to configure one and you're not seeing the setup page there do you reach out to your account team there might be a little bit of setup that needs to happen on our end first so nothing's wrong just a quick extra step and when you're using an external authentication method our biggest trick is to make sure that you're using the test buttons that are available throughout the configuration pages these test buttons are especially important to make sure that your configuration is working correctly and as expected since a lockout is something we definitely want to ignore not ignore prevent ignoring it is another option too but maybe not the most ideal the test buttons are available in the configuration pages of all four of those different authentication systems so they're totally available and quick and easy to use a quick note about them is that the success message that appears at the top as we can see here is only looking for if it the authentication itself is working correctly this is a great thing and a first step when you see the success message awesome my configuration looks like it's working perfectly I can totally go in and able it now woohoo I did it not quite there's one other thing we want to make sure we check and that's the user info box this is especially important if you're using group 2 role mapping in this case you can see the groups and roles in this user info are blank if I was expecting my role to be assigned through this authentication this would be an upsetting piece of information and would give me a hint that I need to go check my configuration settings and be sure that my sam'l groups are called what I'm expecting them to be called I didn't have a typo anywhere and that when a user logs in they will be assigned the role that I am expecting them to be assigned all right Thank You Rachel so we're gonna switch gears a little bit and now we're gonna talk about monitoring so you can use a tool in Logar called a looker to monitor what's going in your incense and we will chat about that now so as admins hopefully most of you are familiar with the usage dashboard the usage dashboard which we're showing you here can be found in the admin section if you scroll all the way down to the bottom of that left-hand nav and you can see maybe you can't see it on the back but there is a tab there called usage the very last one on the list and if you click into that you'll get this dashboard and this dashboard is giving you some high-level insights about what's going on in your look or instance so this dashboard contains about eight or ten tiles you can't see them all here but I'll walk you through what's on this dashboard at the top you have a tile for queries by source so this is the top one that you see here and this tile is going to show you where your users are executing different queries and so you can see the pink here on the stack chart is dashboard queries the teal is Explorer queries so I can immediately see that my users are getting their data more often from dashboards than Explorer's depending on your goals that might be something you want to adjust and it's just kind of a good thing to know where in the application your users are spending most of their time below that you have two tiles that give you some info about users the first is showing you active users per day and in ila per and in the usage dashboard when we talk about active users we're talking about users who are querying so users who are running a query we call those active so this first tile on my right it's showing you active users per day so you can see how many people are using Walker on a daily basis next to that we have a tile for top users which is a little cut off and I've blurred out the names because we're admins here and we care about security and privacy of our users but if you could see the names on this tile you would see a list of the the folks who are users in my instance who are querying the most and that's an important thing to know because you can align with those use and get them to help evangelize and spread the use of data in your organization below those tiles there's some information about query run time so you can get some performance stats some info about scheduled plans showing you performance and status of those schedules below that is the tile for public looks and a tip we want to throw out for that one this is the tile that you should keep an eye on if you're an administrator and you've opened up access for your users to make certain looks public you should keep an eye on that tile in this dashboard because you really should only be exposing data that is truly public make sure that no sensitive data is being shared by your users and then finally at the very bottom of this dashboard you'll find tiles for the top looks the top dashboards and the commonly used fields which will give you some insights into what's the most popular stuff that your users are using so this is a great high-level view and the usage dashboard is going to give you a bunch of info but it also serves as a launching point that's going to get you into the I look er explores so I look ur is a model that's built into your looker in sense built for you by us at lookers it's not one that you can find or see on your own it's a little bit hidden but this I look ER model connects directly to the internal application database in looker so it's letting you peek under the hood and see what's going on in your instance across several different dimensions and so to get to those I look up scores because they're a bit hidden in the product today you can use the usage dashboard and click into any of the tile titles or open that drop down menu and click explore from here so you might be wondering if these are hidden why should you dig into these I look at explores what good stuff is there well for one the eye Locker explorers are what's powering this entire dashboard so everything that you find in the dashboard you can drill and deeper by going to the explorers and there's four important use cases that we're gonna walk through in a second here that are really great things that you can do with ilogger so the first one that we're gonna walk through is using Isla / you can see what's most popular in your instance the second use case that's really handy is using eye Locker to monitor issues problems that your users are running into so you can start to troubleshoot those the third use case is getting alerts on things that are changing or events that are happening within your incense and then finally the fourth use case we'll talk about is knowing who's active and who's not as active in your instance so we're gonna dig into that first use case now and imagine that I actually clicked on that Explorer from here button in this dashboard that's gonna take me to and one of the I'll occur Explorer is called history so the history Explorer you can navigate to it the way I just described but you can also go directly to the URL so you might want to jot this one down the URL for this is gonna be your hosts you fill that in with whatever your organization's host name is don't look your comm slash Explorer just like any other Explorer / I looker with a double underscore it's two underscores there slash history and so this Explorer is based on the history table in the internal database of looker and the history table stores query history so every query that your users have run in the last 90 days has a record in this table and keep in mind it does get truncated after 90 days so in this Explorer we've joined in a bunch of other tables to give that query history some context so we've joined in a table for dashboards for looks we joined in some user information so you can start to get some interesting insights out of this Explorer and some of the top use cases for this Explorer are seeing what dashboards what looks and what explorers are most popular in your instance and these are important things to know because that tells you what content and what parts of your model your users are most engaged with it can also start to surface problems for example if you or your team has spent a bunch of time building out a really complicated dashboard or model and you go to this query Explorer history Explorer and find out that nobody's using that stuff that might be an opportunity for you to adjust your model or adjust your content or reach out to your users and provide some training to get them more engaged with that content so we'll walk through a couple of quick examples using the history Explorer so I apologize that it's a little bit small I realize you guys probably can't read this so I'll just walk you through it so what I've done here I'm in the history Explorer and I pulled in some information about dashboards so I pulled in a dashboard title and I've also pulled in a measure called query run count and the query run count is telling me how many queries were run against each of these dashboards and I've applied a filter here for the last seven days so this is going to show me which dashboards have been the most popular in the last seven days another good use case is seeing what's the most popular looks in in your incense so here I've swapped out the dashboard title and pulled in a look title and said and I'm also pulling in some interesting metadata about looks so I pulled in a created date for the looks and I've also pulled in this third column here which is called a look link and so within the eye locker model you'll find some fields that are built to be links that will take you to other parts of the look or application in this case this link is gonna take me directly to that look so if I'm looking at data about that look and I want to figure out exactly what it is I don't have to search for it I can click right through from that dimension I'm pulling in an additional measure as well so I still have my query run count and the second measure that I'm pulling in is called average run time so the average runtime field is going to tell me how long queries are typically taking and this is a really interesting measure to juxtapose against your query run count because then you can see of the most popular data or of the most popular content that your users are looking at how many of them are performance and if you find that your most popular look has the longest average run time that's an opportunity to go and make sure that that content that your users want is going to run quickly and then finally I'm taking a look at the most popular explorers in my in sense and so here I pulled in from the query table a dimension called Explorer which is giving me the name of the Explorer that users are querying and here again I'm still using the query run count to sort through and show me the most popular explorers but I've pulled in a second measure which is a user count and so again another interesting one to compare to the average or sorry to the query run count to see how many of your users are actually running those queries and in this example you can't the second row here the second most popular Explorer is called events and it has the second highest query run count but only five users using it so this is probably an area where I want to dig in I can click on that five in the user count column and see who those users are and probably want to reach out to them and find out what are they doing that they're querying this Explorer so much all right so that's the first use case looking at what's the most popular stuff in your instance the second use case that we want to talk about is monitoring problems so looking for areas where your users might be running into queries that are airing out or schedules that are failing so in this example I'm still using the history Explorer and I've pulled in a new field that I'm using as a filter and this field is called status so this is the status from history table so it's the status of the query and I'm filtering for statuses that are equal to errored or kilt and I've pulled in a new dimension as well called history source and the history source field is going to show you from where in the looker instance your users executed that query so in this list here the source is our sequel runner Explorer the API dashboards just to give you a feel for what might come up so in this case I can see that on explores in the last day because I filter for one day two of my users have run into errors or queries that have aired and two of them have killed queries so I might want to drill in there so I'm gonna drill into the errors and I blurred out the names but I can see exactly which user ran into this problem I see that he it looks like he ran the same query twice and got errors both times I can see which Explorer he was trying to hit which model and if I click into that it's very hard to see but there is a little drop-down menu button which is circled here and if I click in there I'll get a link that will take me to this query this arid query on the query details panel which is another page in the admin section and from there I'll be able to see the exact error message that my user encountered and I can start to drill in and figure out what's going on and where I can make improvements to make sure no one else runs into the same errors another good one to monitor is schedules so this is a new or a different I love her Explorer this one is called scheduled plan and so that's a URL in case you wanted to jot it down and the scheduled plan Explorer is going to show you information about schedules that you have created or your users have created and it's going to give you some interesting details like job counts and destination and formats so from here I'm going to query to see how many schedules have failed in the last 24 hours and so I've pulled in the name of the schedule and the number of times of that schedule has run when and filtered on a status field specifically looking for failures and so I can see that in the last 24 hours 6 schedules have failed in my instance and I can start to drill in here and start to figure out what's going on and where I can make improvements and I should point out too there is a page in the admin section called scheduler history which contains a lot of the same information but that page is showing you the most current schedules that have run that have either resulted in a success or a failure what's great about having access to this Explorer is that in addition to having that running list and that admin page from this Explorer you can start to dig into more historical data are looking for patterns and see where there might be failures that you can avert or prevent alright so this brings us to our third use case so we've talked about using I liquor to look for the most popular stuff and to look for problems that your users might be encountering you can now save or I shouldn't say now you've always been able to save and schedule important reports in eye locker just like you can with any other data that exists in looker so from any of these eye locker explorers I can click into the the gear menu and I can save these things as looks I can see them as a dashboard you can build your own monitoring dashboard off of I'll ever that will be pretty cool customize it for your needs and I can also schedule this content so here we've gone back to that previous example that I gave where we're in history Explorer and we're looking for queries that have aired or been killed this might be a report that I want to get to my inbox on a daily basis so that I can stay on top of the problems that my users are encountering so I can do that just by using lookers normal schedule functionality another thing you might want to schedule our events so things that happen or change in your look or instance so this brings us to a third eye looker Explorer that we're gonna describe for you today this Explorer is called event attribute and the event attribute Explorer is giving you information about events that are happening in your looker instance and it's this one does get truncated as well so it's going to hold up to a hundred thousand rows of event data so this is good for scheduling if you just want to see kind of the most recent things that have happened and get alerts based on those things you can use this Explorer so in this example here I want to know as an administrator when changes are being made the users in my instance so I have filtered on the on three events I'm looking for events that are creating a user deleting a user or updating a user and I'm filtering on the last day and I can see here that in the last day five new users have been created I can explore a little further from here and see who those users are that were created and which user created them so this might be something that again I want to schedule to myself some of these events that exist in the event attribute table you might want to schedule out to your security team for example using the scheduler functionality you can send any reports to another team or another department in your organization we do want to point out that if you are sending things over email you should not put in PII so you can get email addresses out of the user the user joins in many of these explorers so focusing on names or ideally user IDs is going to be your best bet if you're sending data across to other departments all right and so finally we're on our fourth use case and so this is one of my favorites you can use a looker to see who's active in your instance and so the example that I have up here is going back to that history Explorer and this is a really good place to look for those active users because it is querying all of the query history varying the query history so so in this example here I've pulled a simple list with user names which I've blurred out again and I pulled in two measures for approximate web usage in minutes which is a feel that we're calculating for you and again the query run count and so from this view I can see who most active users are how much time they're spending in the application and an interesting thing that you can do here you can also sort this in the opposite way and see who some of your least engaged users are and a great customer story that I have I recently talked to a customer who was using a looker to find unengaged users in her company and she was responsible for training on the data team so she was responsible for training the rest of the company in their data and she was using this Explorer to find users who were not engaged who are not querying workers and she would then go and physically sit near them in the office she would find where their desk was and she would go and sit near them and what she found was that being physically present people were more open to asking her questions about the data that they were probably stumbling with on their own and we're just too shy to ask so that's one of my favorite examples of kind of the things that you can do the optimizations that you can make and get creative with using the data in I'll occur and then finally this is again that same Explorer and here I pulled out the user names and pulled in a week dimension and now I'm looking at user counts trending over weeks and so this looks like I've got between 50 and 60 users actively querying on a weekly basis it's pretty good depending on how many users are actually in the in sense and so this is another very handy metric to have and to keep an eye on and just to give you another customer story I talked to a customer who was the head of his data team and his team looks at this metric in ilogger they call it the weekly active looker metric and they look at it every week and they use it to optimize what they're doing as a team what content they're building out how they're training their users and they're really optimizing to increase the number of users in their company who are using data to do their jobs and doing that through liquor so handy thing to have to save and keep an eye on already so that concludes the the talk on I look ER but before you go I want to give you a sneak peek you probably noticed by my showing you URLs and talking about how some of these I love her explores are a little bit hidden in the product you're probably wondering what are we doing to improve that to make that better and I'm happy to announce that we are working on improvements to I liquor and the usage dashboard and so coming very soon and you'll hear more about this in the keynote tomorrow coming very soon are some admin tools that we're building to make it easier for you to do all of this query so pre building it for you so we're building out we're improving the ilyich remodel we're actually overhauling it and creating a new model called system activity and with that rollout we're also giving you three pre-built dashboards to replace that usage dashboard so here you can see the first of those dashboards is called user activity I'll walk you through the other three in a second but the the goals of this project are one to make the data in this model more understandable starting with a name change so I liquor has been confusing for several folks it doesn't really tell you what the feature is what it does we've renamed the model system activity and so that hopefully kind of demystifies it a bit and when you talk about it in your organization other people can jump on and use it as well with more understanding we're also working on better documentation so before this feature gets out of beta we have a goal to add definitions to every field in the Explorer's right now many of the fields are undefined and that can be a little bit of a confusing experience to try to build a query when you don't really know we what those feel to me so better documentation is coming soon we're also working on improving the user experience so for one thing we're giving you pre-built dashboards so hopefully you don't have to build as much data but you can continue to drill in and we want to give you all the flexibility that you need so all of the Explorers in this new system activity model are going to be accessible from the explorer drop-down for admins and folks with a special permission to see that stuff so as admins you can also choose which admins in your organization you want to open this stuff up to and give them a special permission called see system activity which exists today and you can give them access to I look ER as soon as you go home if that's relevant and then finally we're also building out more content and some new explores so throughout the year the coming year you'll see us continuing to improve in this area even after we launched it which will be before the end of the year so this is the first dashboard the user activity dashboard this one is a Content activity dashboard giving you some information about content in your system so that's popular stuff that's unused and then finally a big dashboard for performance audits so this one is going to give you a lot of high-level information about how things are running in your system so you can make sure that everything is running smoothly and you'll see more of all of these tomorrow morning you