<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Eric Arsenault on Medium]]></title>
        <description><![CDATA[Stories by Eric Arsenault on Medium]]></description>
        <link>https://medium.com/@eric-arsenaults?source=rss-b834b13dd535------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XBig3h0MbXy-qCRqvJCE8Q.png</url>
            <title>Stories by Eric Arsenault on Medium</title>
            <link>https://medium.com/@eric-arsenaults?source=rss-b834b13dd535------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 08:01:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eric-arsenaults/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[My Favorite AI Coding Tools in 2025]]></title>
            <link>https://eric-arsenaults.medium.com/my-favorite-ai-coding-tools-in-2025-d2a72607edd8?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/d2a72607edd8</guid>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Wed, 17 Sep 2025 03:56:15 GMT</pubDate>
            <atom:updated>2025-09-17T16:09:47.663Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LC0_HYthdiWnCnEg" /></figure><p>As an engineering manager in 2025, I’ve seen firsthand how AI coding tools have transformed the way engineering teams work. These tools aren’t just about speeding up the coding process; they’re reshaping how engineering teams collaborate and innovate. With the ability to generate code snippets, assist in debugging, and even explain an entire codebase, these tools empower teams to focus on what truly matters — providing business value.</p><p>In this article, I’m excited to share my favorite AI coding tools of 2025. I’ll highlight what makes each tool unique, their standout features, and their pricing structures. By the end, I hope you’ll have a clearer idea of which tool could best support your team’s needs and help you lead more effectively.</p><h3><strong>1.) OpenAI Codex</strong></h3><p>OpenAI Codex is an AI coding tool developed by OpenAI, the creators of ChatGPT. It has gained significant attention for its ability to understand and generate code across a variety of programming languages, translating natural language prompts into functional code.</p><p>What truly sets Codex apart is its versatility and utility. It supports a wide range of programming languages and can be accessed in their cloud UI, through their CLI, or with their integration with Visual Studio Code and popular forks like Insiders, Cursor, and Windsurf. For devs on the go, Codex even features a mobile app that allows users to track progress, review pull requests, and merge changes from their phone.</p><p>Codex is a comprehensive suite that goes beyond mere code generation; it can also debug code, perform code reviews in Github, and even explain how code works. These advanced features make a very robust tool that can help to fill gaps in your team’s capabilities where needed.</p><p>In terms of pricing, OpenAI Codex operates on a pay-as-you-go model based on API usage. This flexible structure allows users to pay only for what they use, avoiding long-term commitments. While there is no fixed subscription fee, costs can vary depending on the volume of requests made to the API. This pricing model is particularly appealing for startups and smaller teams with fluctuating needs, as it enables them to scale their usage according to project demands.</p><h3><strong>2.) GitHub Copilot</strong></h3><p>Copilot is a revolutionary AI-powered coding assistant created by Github that has quickly become a favorite among developers. Copilot leverages advanced machine learning models to provide context-aware code suggestions directly within popular IDEs like Visual Studio Code, JetBrains, Azure Data Studio, Xcode, Vim/Neovim, and Eclipse. It can also be used on the GitHub website, through the GitHub CLI, and using GitHub Mobile.</p><p>One of its standout features is its ability to autocomplete entire lines or blocks of code based on the context of what the developer is currently working on. This not only speeds up the coding process but also helps reduce the cognitive load on developers, allowing them to focus on higher-level problem-solving. Although this feature is popular, Copilot’s AI tools go beyond code generation and completion. It can assist with every phase of the software development lifecycle; planning, code creation, code reviews, testing, deployment, and operations.</p><p>What makes GitHub Copilot unique is its deep integration with GitHub’s vast repository of open-source code. By training on a diverse range of codebases, Copilot can generate suggestions that are not only syntactically correct, but also aligned with best practices in various programming languages. It supports a wide array of languages, including Python, JavaScript, TypeScript, Ruby, Go, and many others, making it a versatile tool for companies with many different types of projects. Additionally, Copilot can adapt to a developer’s coding style over time, providing increasingly relevant suggestions that fit their specific workflow.</p><p>In terms of pricing, GitHub Copilot operates on a subscription model. As of now, it costs $10 per month or $100 per year for individual users. For organizations, there are tailored plans available that can accommodate teams of various sizes. This pricing structure makes Copilot accessible to both individual developers and larger engineering teams, allowing them to leverage its capabilities to enhance productivity and collaboration.</p><h3><strong>3.) Claude Code</strong></h3><p>Claude Code is an innovative AI code generation tool that has gained traction for its advanced natural language processing capabilities. Developed by Anthropic, Claude Code is designed to assist developers by translating natural language prompts into functional code across various programming languages. Claude Code excels at both routine development tasks like bug fixes and testing, as well as transformative work like refactors and feature implementation that require deep codebase understanding.</p><p>What sets Claude Code apart from other AI coding tools is its emphasis on safety and ethical considerations in AI development. The tool is built with a strong focus on minimizing harmful outputs and ensuring that the generated code adheres to best practices. Claude Code never modifies your files without explicit approval, and adapts to your coding standards and patterns. This approach not only enhances the reliability of the code produced but also fosters a more responsible use of AI in software development.</p><p>Additionally, Claude Code supports a variety of programming languages, including Python, JavaScript, Java, and C++, and can be used in their UI, through their CLI, or in popular IDE’s like VS Code and JetBrains.</p><p>In terms of pricing, Claude Code typically operates on a subscription model ranging from $17 — $200 per month based on the user’s needs and the scale of usage. It is generally positioned as an enterprise-focused solution, catering to teams and organizations looking to integrate AI capabilities into their development processes as opposed to individual developers or hobbyists.</p><h3><strong>4.) Cursor</strong></h3><p>Cursor is an AI-powered coding assistant designed to enhance developer productivity by providing real-time code suggestions and completions. One of its standout features is its ability to seamlessly integrate into various IDEs, allowing developers to access its capabilities without disrupting their workflow. Cursor excels at understanding the context of the code being written, enabling it to generate relevant snippets and suggestions that align with the developer’s intent. This context-aware functionality not only speeds up the coding process but also helps reduce errors, making it easier for developers to focus on building robust applications.</p><p>What sets Cursor apart is its unique features and emphasis on collaboration and user experience. The tool is designed to facilitate teamwork by allowing multiple developers to work together in real-time, sharing code snippets and suggestions as they go. This collaborative aspect is particularly beneficial for teams working on complex projects, as it fosters communication and ensures that everyone is on the same page. It offers unique features like rules, memories, and ignore files that can help your AI agents write code that is up to your companies standards. Finally, it integrates with Github and Slack for collaboration across the entire engineering team.</p><p>In terms of pricing, Cursor offers a flexible structure ranging from $20-$200 per month. For teams and organizations, there are paid plans that provide access to advanced features and enhanced collaboration tools. The pricing for these plans varies based on the number of users and the specific features required, making it accessible for both small teams and larger enterprises.</p><h3><strong>5.) Windsurf (formerly Codeium)</strong></h3><p>Windsurf is an emerging AI coding tool that has quickly gained popularity for its user-friendly interface and robust functionality. Designed to assist developers in writing code more efficiently, Windsurf offers features such as real-time code completions, code reviews, and the ability to generate code snippets based on natural language prompts. One of its standout features is its speed; Windsurf is optimized for quick responses, allowing developers to maintain their flow without interruptions.</p><p>What makes Windsurf unique is its commitment to being a free tool while still providing powerful capabilities. Unlike many other AI coding assistants that require a subscription, Windsurf offers a generous free tier that includes essential features, making it accessible to a wide range of users from students to professional developers. Additionally, Windsurf supports many programming languages including Python, JavaScript, TypeScript, C++, and more, which enhances its versatility and appeal to developers working in various domains. At the time of writing this article, Windsurf supports 40+ IDEs and 70+ coding languages.</p><p>In terms of pricing, Windsurf stands out for its free access to basic features, which allows users to explore its capabilities without any financial commitment. For those who require more advanced functionalities, Windsurf also offers premium plans that provide additional features and enhanced support. The pricing for these premium plans ranges from $15-$60 per month, making it an attractive option for teams looking to integrate AI code generation into their development processes without breaking the bank. Overall, Windsurf is a powerful tool that not only enhances coding efficiency but also democratizes access to AI-driven development resources, making it a valuable asset for developers at all levels.</p><h3>Conclusion</h3><p>The landscape of coding in 2025 has been undeniably changed by the rise of AI code generation tools. As we’ve explored, tools like OpenAI Codex, GitHub Copilot, Claude Code, Cursor, and Windsurf each bring unique features and capabilities to the table. These tools not only streamline the coding process but also foster innovation by allowing developers to focus on higher-level problem-solving and creativity.</p><p>As an engineering manager, leveraging these AI tools can significantly enhance your team’s productivity and effectiveness. By understanding the strengths and pricing structures of each tool, you can make informed decisions that align with your team’s specific needs and goals. Embracing these technologies will not only help you lead your team more effectively but also position your organization to thrive in an increasingly competitive landscape.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d2a72607edd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Reduce Data Platform Spend in 2023]]></title>
            <link>https://eric-arsenaults.medium.com/how-to-reduce-data-platform-spend-in-2023-57c308dc965a?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/57c308dc965a</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Fri, 21 Jul 2023 20:26:07 GMT</pubDate>
            <atom:updated>2023-07-21T20:26:07.833Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*huzLBkOa9Zx7PkNp.png" /></figure><p>2023 has been a hard year to run a data platform. Across the board it seems like the collective theme of the year has been cutting costs. A few years ago it felt like a lot of companies ran their data platform like the old saying “throw enough mud at the wall, and some of it will stick.” Unfortunately data costs can get out of hand pretty quickly and this year’s tumultuous market has made a lot of companies reflect on their data spend with more scrutiny. It has left companies wondering if they can actually prove ROI to justify their data platform costs. Although data is essential to almost all modern businesses, a lot of companies over-spend, especially when the tech sector is in a bull market and budgets are loose. This is not true this year for most companies, so in this article I will list five ways that you can cut costs in your data platform:</p><ol><li><strong>) Clearly Define ‘Business Critical’ Stakeholder Needs </strong>— The first thing to do when you need to cut costs in a data platform is to meet with your stakeholders to clearly define their needs. The goal here is to explicitly define what they need, why they need it, and the details around delivery. If the data platform team does not clearly understand what the stakeholders need it is impossible for them to deliver the data in a cost effective manner, because they are making assumptions about the minimum requirements. Also, if they don’t clearly understand why the data is needed they will not be able to efficiently prioritize the requests that are most important to the overall objectives of the company. Data platform teams should work with their stakeholder groups to build stakeholder agreements around their data needs. Some things that I like to include in these agreements are:</li></ol><ul><li>What data is needed?</li><li>Who need access to the data? Which people/systems?</li><li>When do they need it? Refreshed at a specific time or event?</li><li>Where does the data need to be stored? What format?</li><li>Why are we doing this? Does it directly relate to the company objectives and priorities? Can we track the ROI?</li><li>How will it be accomplished? Who will do the initial work? Who will support future maintenance and features?</li><li>Info on data governance and quality standards like uptime, acceptable error rates, availability, deprecation info, etc…</li></ul><p>Although this may seem tedious, going through this exercise with stakeholders on a regular basis will help the data platform team to understand stakeholder usage and ultimately decide what defines business critical data. From there, it is then the job of the data platform team to decide what data to expose to users and how they can do that in a cost effective way.</p><p>Priorities amongst business users can change fast, and after going through this exercise sometimes companies find that they are overpaying for data services that don’t actually make a big impact on the company. They may also find that some requests for new work do not truly align with the success of the company objectives, and implementing them brings no ROI. After finishing this exercise a data platform team should fully understand the needs of their stakeholders and how they relate to the objectives of the company. They should then be able to use that information to design and implement a system that meets the minimum stakeholder requirements while still staying within budget for the company. Without fully understanding what is needed and why it is needed, its impossible for the team to deliver the lowest cost option.</p><p><strong>2.) Prioritize Stakeholder Deliverables —</strong> If you give a mouse a cookie….they will ask for 5 new data sources added to their data model. Just kidding- but there is some truth there. It is important to work with your stakeholders and make sure that everyone understands that the amount of work that you can deliver is limited by the budget given by the company.</p><p>Stakeholders usually want more data than they truly need to get their job done, and data platform teams usually want to deliver the minimum amount of data they can to reduce headcount and operating costs. This leads to a disconnect; stakeholders want all the data they can get, and data platform teams want to give them the minimum amount that they need to be successful. Ultimately someone needs to decide what is truly business critical and what is just ‘nice to have’. This is the job of the data platform team; they must decipher what is actually needed and what is not important. As crucial as it is to fulfill stakeholder requests, it is even more important to say ‘no’ to the requests that you can not implement or believe are not necessary. In most cases if data teams were to deliver everything that stakeholders ever asked for, they would need a huge team with an unlimited budget.</p><p>What is actually delivered to stakeholders should be determined by the needs of the company. All analysts and engineers can relate to this scenario; you receive a request and after researching it further you learn that it is not related to the objectives or mission of the company. The stakeholder was just experimenting or doing something they think is interesting that is vaguely related to their job. In situations like this, it is critical that data teams determine why they are completing a request and not just take the stakeholders word for it. Since the team is limited by the budget they are given, they must make sure they are prioritizing the work that is most important to the company.</p><p><strong>3.) Track Expenses like a Hawk —</strong> It is important now more than ever to watch your costs closely. Most companies are looking to cut costs this year while large cloud providers are simultaneously jacking up prices. In the past year we have seen a big price hikes from managed data tools providers like Google and dbt Labs. With prices rising it is crucial to have good cost management practices and make sure you are not also experiencing unexpected or unnoticed cost anomalies.</p><p>One thing is for sure, the only way that you will notice price anomalies in your data platform is if you are keeping a close eye on them. When cost and usage spikes go unnoticed it can end up being very expensive when the bill is due. Unfortunately it can also be difficult to notice them; Data platforms are complex and are usually not setup with any type of cost or usage alerting out of the box. Even once they are tracked, it can be hard to isolate the root cause of a price anomaly and articulate that to the rest of the team. Luckily there are tools out there for tracking and alerting on cost and usage spikes that you can use to autonomously alert your team. If you are using one of the large cloud providers you can use the built in tools like <a href="https://cloud.google.com/products/operations?hl=en">Google Cloud’s Operations Suite</a>, <a href="https://docs.aws.amazon.com/cloudwatch/index.html">Amazon CloudWatch</a> or <a href="https://azure.microsoft.com/en-us/products/cost-management">Microsoft Cost Management</a>. If these tools do not work for your data platform infrastructure you can also use third party tools like <a href="https://www.cloudzero.com/">Cloud Zero</a>, <a href="https://www.harness.io/">Harness</a> or <a href="https://www.datadoghq.com/">Datadog</a>. Whichever tool you choose, be sure that you are tracking cost and usage spikes and pushing alerts autonomously to the proper team members to fix.</p><p><strong>4.) Audit Old Code and Clean Up Stakeholder Trash —</strong> Unless you work at a brand new start up with all new employees and greenfield work, there are probably some old data assets that can be cleaned up or deleted all together. Most data platforms have a good bit of bloat, and development usually outpaces depreciation to a large degree. After years of this it can sometimes be hard to tell what is still needed and what is stale code that is just wasting money in the data platform because everyone is afraid to delete it. To put it bluntly, prior years trash is usually still being run in most data platforms. Data platforms teams must monitor usage and clean up this old trash that is still in the system, otherwise it will continue to leak money and add latency.</p><p>Beyond that, it is also essential to periodically clean up after the stakeholders. Remember that stakeholders are not responsible for the health of the system and they will rarely, if ever, clean out old stuff on their own. They won’t delete old dashboards and schedules, request for an old table to be dropped, or ask for a data pipeline to be deleted. These are cost containing decisions that the data platform team needs to make after defining stakeholder need and reviewing usage. Leaving these things running without periodic clean-ups is like throwing money out the window.</p><p><strong>5.) Use Open Source and Inexpensive Infrastructure when Possible —</strong> While there is usually great benefit to using expensive and proprietary data tools, there is also significant downside when looking at the cost. These tools are amazing; they empower the masses to perform intense modern analytics at the snap of the fingers with very little setup, but they come with a high price tag that can not be ignored. While most companies can not get away from using expensive tools completely, it is important to properly assess when you need to use expensive tools and when something more cost effective will work.</p><p>Here is an example; lets say I am working with a company that uses Snowflake as their main data warehouse. Snowflake is expensive but it is necessary for the company’s production environment. This is because of the use case; there are tons of users running lots of concurrent queries at once that all expect high availability and low latency. Using a lesser data warehouse would simply not work for the production environment, but this does not mean that the entire data platform needs to be built using Snowflake. There are still opportunities to use a less expensive database like PostgreSQL for development. For example, I can cut costs by running all of my dbt tests and development to this database, and since dbt handles the DDL all of the modeling code can be the same between systems. Since development environments generally do not have the same frequency of queries or availability requirements as production, it does not necessarily need to be built using Snowflake. Using PostgreSQL is a big savings since you can start a managed instance for a low monthly cost and do not need to pay per transaction, which can account to a savings of hundreds to thousands of dollars a month depending on your usage.</p><p>The important piece here is not simply to use PostgreSQL instead of Snowflake because it is less expensive, it is to let the use case drive the solution that you choose. Don’t spend money simply to say you are following ‘best practices’ without thinking about alternate solutions. In this case a production environment needs to use an expensive data warehouse because the use case necessitates it, but a development environment does not have the same requirements so it can use a less expensive option. We chose each option because of what the use case called for, and let the needs of the company drive the decision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=57c308dc965a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[django-build-tool: An Open Source Orchestration Tool for dbt Core]]></title>
            <link>https://eric-arsenaults.medium.com/django-build-tool-an-open-source-orchestration-tool-for-dbt-a5069dfdadcb?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/a5069dfdadcb</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Thu, 13 Jul 2023 01:30:26 GMT</pubDate>
            <atom:updated>2025-06-26T17:40:18.558Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/700/0*j1CF-vBo8saESjCt.jpg" /></figure><h3>Introduction</h3><p>Since its release over 7 years ago dbt Core has become a staple in many companies data platforms. Since it is an open source tool, there are quite a few options for deploying jobs in production. Over the past 4 years I have used dbt a lot and have seen it deployed in many different ways. Despite seeing many creative deployment methods, I have always felt like there was not a great tool for deploying dbt projects easily and for a low cost. Despite dbt Core being such a great and powerful modeling tool, I have struggled to decide what the best and most cost effective way is to manage a project. I always felt like there should be a free open source option for deploying and running a project in the cloud for a low cost. I wished that there was an open source orchestration tool for executing dbt Core jobs that I could use without all the work that comes with Airflow. After gathering feedback from other engineers that use dbt Core and have similar experiences, I decided to build one. After successfully using it for a while I have decided to release it for free for anyone else who may resonate with the pain points I have written about.</p><h3>Background</h3><p>As we all know dbt Core is an open source tool, but the open source components are not enough to manage a project in production. Dbt Core is just a simple CLI, it does not include a lot of the components that you need to manage a project. Components like a scheduler, metadata database, REST API, or any other infrastructure. Since it is just a CLI, dbt Core also does not take a lot of computing power to run; most of the heavy lifting is done by the data warehouse while dbt Core is simply waiting for a response. When taking these points into consideration it is hard to justify the prices that some commercial SaaS solutions charge. It is also important to consider that the amount you pay to actually execute jobs is only a small fraction of the total cost you are paying to use this transformation method; the majority of the cost will be on the data warehouse bill. It remains debatable how much money you should spend to transform your data, but it is clear that the cost to simply run the jobs should be kept as low as possible.</p><p>While there are some other open source platforms that can be used to cut costs like Airflow, they are not setup to run dbt out of the box and there is some coding and configuration needed. Beyond that, custom builds can range in cost and complexity.</p><p>All of this has lead to some ambiguity; there is not one objectively correct way that dbt Core must be managed to be successful, and a lot of companies are grossly overpaying to use it. Despite working with companies managing dbt in a number of ways, all of the solutions have had some negatives and I always felt like there should be a better option. I wanted an option with low complexity that also came at a low cost. For these reason I decided to build django-build-tool with the goal of creating an orchestrator for dbt Core that was easy to use and was available at a low (or no) cost.</p><h3>What is django-build-tool?</h3><p>Django-build-tool is an open source orchestration tool that is designed specifically for executing dbt Core jobs. It is built using open source components and is available to use free of charge. You can use it locally, in the cloud or on-premise to orchestrate and run dbt jobs. It is built on open source components; the scheduler and API are built using Django, Celery and Redis, the metadata is stored in PostgreSQL, and the entire project is containerized using docker-compose.</p><h3>Why use it?</h3><p>Django-build-tool has a lot of features that make it an attractive option for managing dbt Core jobs. Some of them include:</p><p><strong>Cost</strong>—One of the biggest reasons to use django-build-tool is the cost. It is free to download and the license costs nothing. It can also be deployed on a pretty small server. I usually deploy it on an Ubuntu server sized 1 vCPU — 2GB / 50GB Disk ($12/month). Your use case may necessitate a larger server, but either way it is safe to say this is a very inexpensive way to run dbt jobs.</p><p><strong>No-Code</strong>— The admin panel of Django is a no code platform. You do not need to write any lines of code to setup and run dbt Core runs using this platform. This is a distinct adavntage over other open source solutions like Airflow. With Airflow you will need to manage the Airflow instance, a DAG, metadata pipeline, database and any extra bells and whistles that you may need like custom operators or event based sensors. Having this stuff setup and available in a no code platform empowers engineers to focus on data modeling and answering stakeholder requests as opposed to writing infrastructure code that is not always visible or impactful to the business.</p><p><strong>Rest API Suite- </strong>django-build-tool comes with a full API suite for tasks within the tool. You can do things like update your profile.yml, add a git repo, or create a new scheduled job using the API. Most importantly it includes an API endpoint to run dbt jobs, which allows users to build event based architecture by triggering jobs from outside systems.</p><p><strong>Open Source Infrastructure-</strong> The components that are used in django-build-tool also bring an advantage in the fact that it is built on popular and well documented open source components. It is built using tried and true components that are often used for workflows much more complicated than running dbt jobs. These technologies are well tested and can easily handle the task at hand.</p><p><strong>License and Ownership</strong>- As mentioned — the license is free. Django-build-tool allows users to use and modify the tool as they please. You also own the dbt and Django metadata, since it is all stored in the backend PostgreSQL database that is part of the deployment. You own everything and can use or modify it however you need without any limitations.</p><p><strong>Extendable</strong>— If you need to add any custom pieces for your use case like new connectors, different dbt version, multiple environments, custom webhooks, etc, the open source license allows you to modify the code. Since it is built using popular and well documented open source components, many software engineers are able to work on the code without a knowledge silo.</p><p><strong>Easy to Use-</strong> The final advantage to using django-build-tool is that is is very easy to deploy and use. It is packaged in a docker container so all you need to do is clone the repo and deploy the container. Once deployed, the platform is very simple and only has one function. It is less complex than other solutions and lowers the barrier to entry.</p><h3>Directions to deploy</h3><p>django-build-tool can be found on my Github page here:</p><pre>https://github.com/eric-arsenault/django-build-tool</pre><p>To deploy, clone the git repo onto your server or machine and start up the container. During the deployment process, a password file will be created in the project with unique passwords for the Django and PostgreSQL instances. Once the deployment is finished, you can check the password file for the credentials. Do not delete the password file.</p><p>As an example, here is how I deploy django-build-tool on Ubuntu servers in the cloud:</p><pre>&gt;&gt;apt install docker-compose<br><br>&gt;&gt;git clone https://github.com/eric-arsenault/django-build-tool.git<br><br>&gt;&gt;cd django-build-tool<br><br>&gt;&gt;docker-compose up <br><br>...open a new terminal...<br><br>&gt;&gt;cd django-build-tool/passwords<br><br>&gt;&gt;cat password.txt</pre><p>This will deploy django-build-tool on the server and open the credential file giving you the log-in information for Django and PostgreSQL. Once you log in to the Django admin panel you can retrieve your API key. To open the admin panel, open a browser with your ip (or localhost) and the 8000 port like this:</p><p><a href="http://64.227.108.66:8000/">http://00.000.000.00:8000/</a></p><p>Or</p><p><a href="http://64.227.108.66:8000/">http://localhost:8000/</a></p><p>To view the swagger documentation for the API, format the link like this:</p><p><a href="http://24.199.98.105:8000/api/docs/">http://00.000.00.000:8000/api/docs/</a></p><h3>How to Use django-build-tool</h3><p>Once you have deployed django-build-tool there are a few steps to getting jobs up and running:</p><p><strong>1.) Setup Profile.yml —</strong>The first thing to do is to setup the Profile.yml file that dbt will use to connect to your database. Django-build-tool uses the Profile.yml file in the same format that you would use it locally, the only difference is that this platform allows users to setup two profiles for a PROD and DEV target. To update these profiles, use the menu on the left side of the screen to navigate to the Profile YAMLs section. Click on the profile that you would like to update and paste in your YAML.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kvusCM_ivWnwP4BEpXmwag.png" /></figure><p><strong>2.) Clone dbt Project Repo- </strong>Next is to clone your dbt project repo. To do this, first setup a Personal Access Token using your git provider. Here is the documentation showing how to set one up in <a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens">Github</a> and <a href="https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html">Gitlab</a>. Set the permissions to allow the token access to clone the repository.</p><p>This token will allow Django to clone your dbt project so it can be ran. Django-build-tool uses git cloning via HTTPS using a personal access token for authentication. Here is an example showing how to input a GitHub repository link with your personal access token:</p><pre><a href="https://my_personal_access_token@github.com/dbt-labs/jaffle_shop.git">https://my_personal_access_token@github.com/dbt-labs/jaffle_shop.git</a></pre><p>Once the key is created, navigate to the Git Repos section in Django. Add a new Git Repo using the button in the top right. Input the repo using the above format with your personal access key:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0nd9V4IfJPQG6JQ-I3Tshg.png" /></figure><p><strong>3.) Setup Job- </strong>Once you have added the repo for your dbt project, you can now setup a recurring job. Use the menu on the left to navigate to the Periodic Tasks section. Once you are on the page, click the Add Periodic Task button in the top right.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hqwu9_GiqwnPslXO6R1KLQ.png" /></figure><p>Now fill out the options and create the periodic task. You must enter:</p><ul><li>A name for the job</li><li>Which Git Repo to use</li><li>Which Profile.yml to use</li><li>Note: Task should always be set to dbt_runner_task and the box must be checked for ‘Enabled’</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9K_g5LwrIP4gB1QVpvjqww.png" /></figure><p>Scroll down and you can choose a schedule for your task. Django comes with a few options for schedules: Cron, Interval, Solar, Clocked. You may also set a start date and time for your recurring job.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CY8GhYXV8cIG5NHaP7wmjg.png" /></figure><p>Finally, in the Positional Arguments input, add your dbt shell command in the following format:</p><pre>[&quot;dbt command&quot;]</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-hZjAFLo8JaTctohCLdHdQ.png" /></figure><p><strong>4.) Retrieve/Manage API keys-</strong> Now that you have logged into the admin panel and setup a job, you can retrieve your API keys to trigger jobs via Rest API. Use the menu on the left to navigate to the Tokens section. Here you can create, update and delete API keys:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OMDI_2WnrHAG-61WjRuShg.png" /></figure><p>Once you have your API keys created, you can do many tasks within the tool via REST API. Here is an example of how you can run a dbt job from an external system using the REST API:</p><pre>curl -X &#39;POST&#39; \<br>  &#39;http://00.000.000.00:8000/api/run-dbt-task&#39; \<br>  -H &#39;accept: application/json&#39; \<br>  -H &#39;Content-Type: application/json&#39; \<br>  -H &#39;X-CSRFTOKEN: my_token&#39; \<br>  -d &#39;{<br>  &quot;task_id&quot;: 1<br>}&#39;</pre><p>To view the full API Documentation, open a browser and follow this link format:</p><p><a href="http://24.199.98.105:8000/api/docs/">http://00.000.00.000:8000/api/docs/</a></p><p>Or</p><p><a href="http://24.199.98.105:8000/api/docs/">http://localhost:8000/api/docs/</a></p><p>Once on this page, you can view the full swagger documentation and test API calls:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ebjmy0H80v3JlHO9oLphrw.png" /></figure><p><strong>5.) View metadata — </strong>After setting up and running dbt jobs, you will need to view the metadata. There are a few ways to view run status and metadata in django-build-tool. The first way is to view this information in the Admin Panel. Navigate to the menu on the left and click the DBT Logs section. Once you are on the DBT Logs page, you can click into each run to view the completion status and metadata:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B1aqo64Buwx9cDCP3UMldw.png" /></figure><p>All of the metadata is also stored in the backend PostgreSQL database and can be queried like this:</p><pre>SELECT * FROM public.analytics_dbtlogs ORDER BY id DESC</pre><p>Django-build-tool captures a few pieces of metadata after each dbt run. All three pieces of metadata are viewable in the admin panel as well as being stored on the the public.analytics_dbtlogs table in the PostgreSQL backend. The three pieces of metadata stored for each run are:</p><ul><li>The <a href="https://docs.getdbt.com/reference/artifacts/run-results-json">run_results.json</a> file created by dbt</li><li>The <a href="https://docs.getdbt.com/reference/artifacts/manifest-json">manifest.json</a> file created by dbt</li><li>The terminal output from the run</li></ul><p>After clicking into an individual run, you can view all of this metadata. Here you can view the manifest and run_results YAML files:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KiCDpvI8BhkR5dm4MRerdg.png" /></figure><p>The manifest file is too large to show an example in this article, but here is is an example of the run_results.json file once it is formatted:</p><pre>{<br>  &quot;args&quot;: {<br>    &quot;vars&quot;: {},<br>    &quot;defer&quot;: false,<br>    &quot;print&quot;: true,<br>    &quot;quiet&quot;: false,<br>    &quot;which&quot;: &quot;run&quot;,<br>    &quot;select&quot;: [],<br>    &quot;exclude&quot;: [],<br>    &quot;log_path&quot;: &quot;/root/.dbt/external-1/logs&quot;,<br>    &quot;log_level&quot;: &quot;info&quot;,<br>    &quot;introspect&quot;: true,<br>    &quot;log_format&quot;: &quot;default&quot;,<br>    &quot;use_colors&quot;: true,<br>    &quot;write_json&quot;: true,<br>    &quot;favor_state&quot;: false,<br>    &quot;project_dir&quot;: &quot;/root/.dbt/external-1&quot;,<br>    &quot;strict_mode&quot;: false,<br>    &quot;profiles_dir&quot;: &quot;/root/.dbt&quot;,<br>    &quot;partial_parse&quot;: true,<br>    &quot;printer_width&quot;: 80,<br>    &quot;static_parser&quot;: true,<br>    &quot;version_check&quot;: true,<br>    &quot;log_level_file&quot;: &quot;debug&quot;,<br>    &quot;populate_cache&quot;: true,<br>    &quot;log_format_file&quot;: &quot;debug&quot;,<br>    &quot;macro_debugging&quot;: false,<br>    &quot;use_colors_file&quot;: true,<br>    &quot;indirect_selection&quot;: &quot;eager&quot;,<br>    &quot;warn_error_options&quot;: {<br>      &quot;exclude&quot;: [],<br>      &quot;include&quot;: []<br>    },<br>    &quot;cache_selected_only&quot;: false,<br>    &quot;enable_legacy_logger&quot;: false,<br>    &quot;send_anonymous_usage_stats&quot;: true<br>  },<br>  &quot;results&quot;: [<br>    {<br>      &quot;status&quot;: &quot;success&quot;,<br>      &quot;timing&quot;: [<br>        {<br>          &quot;name&quot;: &quot;compile&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:17.980266Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:17.984264Z&quot;<br>        },<br>        {<br>          &quot;name&quot;: &quot;execute&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:17.985746Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:18.578344Z&quot;<br>        }<br>      ],<br>      &quot;message&quot;: &quot;SUCCESS 1&quot;,<br>      &quot;failures&quot;: null,<br>      &quot;thread_id&quot;: &quot;Thread-1 (worker)&quot;,<br>      &quot;unique_id&quot;: &quot;model.jaffle_shop.stg_customers&quot;,<br>      &quot;execution_time&quot;: 0.6878182888031006,<br>      &quot;adapter_response&quot;: {<br>        &quot;code&quot;: &quot;SUCCESS&quot;,<br>        &quot;_message&quot;: &quot;SUCCESS 1&quot;,<br>        &quot;query_id&quot;: &quot;01ad73cd-0101-b2da-0000-d5b500505012&quot;,<br>        &quot;rows_affected&quot;: <br>      }<br>    },<br>    {<br>      &quot;status&quot;: &quot;success&quot;,<br>      &quot;timing&quot;: [<br>        {<br>          &quot;name&quot;: &quot;compile&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:18.672652Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:18.678313Z&quot;<br>        },<br>        {<br>          &quot;name&quot;: &quot;execute&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:18.679670Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:19.048538Z&quot;<br>        }<br>      ],<br>      &quot;message&quot;: &quot;SUCCESS 1&quot;,<br>      &quot;failures&quot;: null,<br>      &quot;thread_id&quot;: &quot;Thread-1 (worker)&quot;,<br>      &quot;unique_id&quot;: &quot;model.jaffle_shop.stg_orders&quot;,<br>      &quot;execution_time&quot;: 0.46262216567993164,<br>      &quot;adapter_response&quot;: {<br>        &quot;code&quot;: &quot;SUCCESS&quot;,<br>        &quot;_message&quot;: &quot;SUCCESS 1&quot;,<br>        &quot;query_id&quot;: &quot;01ad73cd-0101-b2e7-0000-d5b500506012&quot;,<br>        &quot;rows_affected&quot;: 1<br>      }<br>    },<br>    {<br>      &quot;status&quot;: &quot;success&quot;,<br>      &quot;timing&quot;: [<br>        {<br>          &quot;name&quot;: &quot;compile&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:19.139196Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:19.143868Z&quot;<br>        },<br>        {<br>          &quot;name&quot;: &quot;execute&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:19.144800Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:19.489356Z&quot;<br>        }<br>      ],<br>      &quot;message&quot;: &quot;SUCCESS 1&quot;,<br>      &quot;failures&quot;: null,<br>      &quot;thread_id&quot;: &quot;Thread-1 (worker)&quot;,<br>      &quot;unique_id&quot;: &quot;model.jaffle_shop.stg_payments&quot;,<br>      &quot;execution_time&quot;: 0.4737679958343506,<br>      &quot;adapter_response&quot;: {<br>        &quot;code&quot;: &quot;SUCCESS&quot;,<br>        &quot;_message&quot;: &quot;SUCCESS 1&quot;,<br>        &quot;query_id&quot;: &quot;01ad73cd-0101-b28f-0000-d5b50050401a&quot;,<br>        &quot;rows_affected&quot;: 1<br>      }<br>    },<br>    {<br>      &quot;status&quot;: &quot;success&quot;,<br>      &quot;timing&quot;: [<br>        {<br>          &quot;name&quot;: &quot;compile&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:19.616571Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:19.621375Z&quot;<br>        },<br>        {<br>          &quot;name&quot;: &quot;execute&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:19.622767Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:20.844456Z&quot;<br>        }<br>      ],<br>      &quot;message&quot;: &quot;SUCCESS 1&quot;,<br>      &quot;failures&quot;: null,<br>      &quot;thread_id&quot;: &quot;Thread-1 (worker)&quot;,<br>      &quot;unique_id&quot;: &quot;model.jaffle_shop.customers&quot;,<br>      &quot;execution_time&quot;: 1.331810712814331,<br>      &quot;adapter_response&quot;: {<br>        &quot;code&quot;: &quot;SUCCESS&quot;,<br>        &quot;_message&quot;: &quot;SUCCESS 1&quot;,<br>        &quot;query_id&quot;: &quot;01ad73cd-0101-b1c4-0000-d5b5004fd046&quot;,<br>        &quot;rows_affected&quot;: 1<br>      }<br>    },<br>    {<br>      &quot;status&quot;: &quot;success&quot;,<br>      &quot;timing&quot;: [<br>        {<br>          &quot;name&quot;: &quot;compile&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:20.952023Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:20.957438Z&quot;<br>        },<br>        {<br>          &quot;name&quot;: &quot;execute&quot;,<br>          &quot;started_at&quot;: &quot;2023-07-06T20:29:20.958294Z&quot;,<br>          &quot;completed_at&quot;: &quot;2023-07-06T20:29:22.061397Z&quot;<br>        }<br>      ],<br>      &quot;message&quot;: &quot;SUCCESS 1&quot;,<br>      &quot;failures&quot;: null,<br>      &quot;thread_id&quot;: &quot;Thread-1 (worker)&quot;,<br>      &quot;unique_id&quot;: &quot;model.jaffle_shop.orders&quot;,<br>      &quot;execution_time&quot;: 1.230893850326538,<br>      &quot;adapter_response&quot;: {<br>        &quot;code&quot;: &quot;SUCCESS&quot;,<br>        &quot;_message&quot;: &quot;SUCCESS 1&quot;,<br>        &quot;query_id&quot;: &quot;01ad73cd-0101-b2da-0000-d5b500505016&quot;,<br>        &quot;rows_affected&quot;: 1<br>      }<br>    }<br>  ],<br>  &quot;metadata&quot;: {<br>    &quot;env&quot;: {},<br>    &quot;dbt_version&quot;: &quot;1.5.2&quot;,<br>    &quot;generated_at&quot;: &quot;2023-07-06T20:29:22.188765Z&quot;,<br>    &quot;invocation_id&quot;: &quot;ec5a7e06-e5f5-4066-82b2-6496aa933dfd&quot;,<br>    &quot;dbt_schema_version&quot;: &quot;https://schemas.getdbt.com/dbt/run-results/v4.json&quot;<br>  },<br>  &quot;elapsed_time&quot;: 5.587259769439697<br>}</pre><p>Scroll down and you are able to view the terminal output from the run that took place:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FvjoBib45BTT4c5rbEW5Vw.png" /></figure><p>Here is an example of a terminal output for Jaffle Shop:</p><pre>[0m20:29:16  Running with dbt=1.5.2<br>[0m20:29:16  Registered adapter: snowflake=1.5.2<br>[0m20:29:16  Found 5 models, 20 tests, 0 snapshots, 0 analyses, 322 macros, 0 operations, 3 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups<br>[0m20:29:16  <br>[0m20:29:17  Concurrency: 1 threads (target=&#39;dev&#39;)<br>[0m20:29:17  <br>[0m20:29:17  1 of 5 START sql view model analytics.stg_customers ....................... [RUN]<br>[0m20:29:18  1 of 5 OK created sql view model analytics.stg_customers .................. [[32mSUCCESS 1[0m in 0.69s]<br>[0m20:29:18  2 of 5 START sql view model analytics.stg_orders .......................... [RUN]<br>[0m20:29:19  2 of 5 OK created sql view model analytics.stg_orders ..................... [[32mSUCCESS 1[0m in 0.46s]<br>[0m20:29:19  3 of 5 START sql view model analytics.stg_payments ........................ [RUN]<br>[0m20:29:19  3 of 5 OK created sql view model analytics.stg_payments ................... [[32mSUCCESS 1[0m in 0.47s]<br>[0m20:29:19  4 of 5 START sql table model analytics.customers .......................... [RUN]<br>[0m20:29:20  4 of 5 OK created sql table model analytics.customers ..................... [[32mSUCCESS 1[0m in 1.33s]<br>[0m20:29:20  5 of 5 START sql table model analytics.orders ............................. [RUN]<br>[0m20:29:22  5 of 5 OK created sql table model analytics.orders ........................ [[32mSUCCESS 1[0m in 1.23s]<br>[0m20:29:22  <br>[0m20:29:22  Finished running 3 view models, 2 table models in 0 hours 0 minutes and 5.59 seconds (5.59s).<br>[0m20:29:22  <br>[0m20:29:22  [32mCompleted successfully[0m<br>[0m20:29:22  <br>[0m20:29:22  Done. PASS=5 WARN=0 ERROR=0 SKIP=0 TOTAL=5</pre><h3>Conclusion</h3><p>Django-build-tool is a free orchestration tool that is designed specifically for running dbt Core jobs. The advantages of using this tool include low cost, modern features and an easy to use UI. It uses open source components and an open source license which allows users to use or modify the code in any way they see fit. Thanks for reading, code contributions and feedback are welcome.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a5069dfdadcb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Data Team Architecture: Centralized vs Hub and Spoke]]></title>
            <link>https://eric-arsenaults.medium.com/data-team-architecture-centralized-vs-hub-and-spoke-879e7b436ed6?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/879e7b436ed6</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[management]]></category>
            <category><![CDATA[company-culture]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Wed, 17 May 2023 01:27:03 GMT</pubDate>
            <atom:updated>2023-05-17T01:27:03.897Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/800/0*CKcrMs6GHZgjL_vy.png" /></figure><p>Data teams are the backbone of any data driven organization, providing essential insights and analysis that inform decision making from the top down. As data teams grow to meet the needs of an organization, it’s important to consider how best to organize them for maximum efficiency and collaboration. Two basic designs for data team architecture are a centralized model and a hub-and-spoke model. Both of these two models for structuring a data team have distinct strengths and weaknesses that should be carefully examined while considering your use-case. In this article we will discuss the differences between these two approaches and provide guidance on which one might be right for your organization. We will also discuss some of the advantages and disadvantages associated with each approach so you can make an informed decision about how to structure your team.</p><h3>Centralized</h3><p>A centralized data team is one that is organized around a single, unified structure and workflow. This type of architecture typically involves a single, central team that serves as the primary source for all stakeholders and data needs. The centralized team will include many team members that all work together towards once common goal. A centralized team may include a manager, data engineer, analytics engineer, data analyst, etc. all working to ensure that data is collected, stored and processed in a consistent manner for the entire organization. Some advantages of this approach include improved efficiency due to streamlined processes and better collaboration by having everyone on the same team. There is less time spent communicating between teams and dealing with the company bureaucracy that comes with it. It also allows for closer management of the team and projects since the entirety of the team members are working under the same management.</p><p>However, there are also some drawbacks to consider as well. For example, if the central hub fails or experiences downtime, it could cause a major disruption to the entire company as opposed to just one single company domain. This can also be very problematic if each role is single threaded and the tasks do not overlap. If someone is on PTO or out sick and there is an outage, it can be much more difficult to get fixed. Also, because of its centralized nature with clearly defined roles it can be difficult to accommodate different skill sets besides the basic tasks that team members perform. Beyond these downsides, another issue is that centralized data teams are harder to scale as one team inevitably becomes un-manageable.</p><h3>Hub and Spoke</h3><p>A hub and spoke data team works by having a central “hub” system that is responsible for managing shared data assets and operations. Using the data from the hub, the specific modeling and analysis can be routed to one or more “spoke” systems. These are distributed members of that data team that work within a specifici company domain. Each “spoke” team specialize in a specific domains of the company and works with a specific group of stakeholders. This provides the “spoke” teams with a high degree of flexibility, allowing them to focus on specific stakeholder asks without having to worry about the health of the entire system. While the “hub” team focuses on the shared data assets and systems that serve the entire company, the “spoke” teams work with specific groups in the company for modeling and analysis.</p><p>Another main advantage of using a hub and spoke architecture for data teams is that it allows for scalability and flexibility. Teams can quickly add new functions or change existing ones without impacting other parts of the business. Spoke teams have the flexibility to build their own modeling and analysis that they can own, as opposed to trying to fit everything into one unified system. This makes it easier to respond to changing business requirements, as well as integrate new technologies into the environment. Additionally, the company can easily add on more “spoke” teams as the business grows without necessarily needing to scale up their ‘hub’ team every time.</p><p>However, there are also some drawbacks associated with this architecture. It requires careful planning when it comes to security and access control since data must be routed through the central hub before it can reach it’s destination. Additionally, having too many spoke teams may result in increased complexity and a disparate and confusing code base if not managed properly. Finally, if any changes are made to the hub then these changes need to be replicated across all of the connected systems in order to maintain consistency. For this reason, it can sometimes be difficult to maintain consistency and data integrity when the team is distributed across the organization and many times working under different management.</p><h3>Which should you choose?</h3><p>Ultimately, making the choice between a centralized or hub and spoke data team comes down to one thing; what best fits the organization’s needs. Companies must consider many things: how much control they want over access and security, how quickly changes need to be implemented across systems and how mission critical fixing broken content is. A hub and spoke system may provide more flexibility in terms of scalability but also requires careful management due its complexity. On the other hand, a centralized approach makes it easier for teams and data systems to stay consistent throughout all projects and changes, but also can be challenging when tasks are not shared and employees are un-availabile. It’s important for companies to evaluate their own unique situation and use case before deciding which option is right for them.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=879e7b436ed6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Hiring for Your Data Team? Here’s What You Need to Know]]></title>
            <link>https://eric-arsenaults.medium.com/hiring-for-your-data-team-heres-what-you-need-to-know-80ba3ace40b9?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/80ba3ace40b9</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Tue, 16 May 2023 01:29:17 GMT</pubDate>
            <atom:updated>2023-05-16T03:40:10.541Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4WD3rXH7toTt7zzZ.jpeg" /></figure><p>Are you looking to hire a new member for your data team? It can sometimes be daunting to hire new employees, but don’t worry — with the right knowledge and strategy, hiring a new team member doesn’t have to be a challenge. In this blog post, we’ll explain the different ways that companies can build successful data teams, from identifying the right skills and roles required to finding the best candidates for the job. So if you’re hiring for your data team and need help, read on to learn more.</p><p>When it comes to hiring members for a data team, there are five key factors that hiring managers need to consider in order to ensure success:</p><h3>Identifying the Roles and Skills Required for Each Role</h3><p>It’s imperative to have a clear understanding of the role and skills required when hiring a new role on a data team. Job titles and responsibilities can vary between different companies; a data analyst or analytics engineer at one company could be a data engineer or data scientist at a different company. It’s important to clarify what you need to ensures that the candidates you interview are best suited for their position. Identifying roles and skills for each member of your data team allows companies to quickly find the right person for each role, reducing time wasted in screening irrelevant candidates that don’t have the skills you need. Having clear criteria in place also makes it easier to evaluate each candidate objectively and fairly as well as providing guidelines for developing any necessary training programs post-hiring. By focusing on specific criteria from the start, companies can save costs by avoiding costly mistakes such as bad hires or overspending on the wrong skill set.</p><h3>Finding Candidates with Relevant Technical Experience</h3><p>After clarifying on roles and skills, hiring someone with the right skills for their role is essential for success. As such, it’s important for managers to make sure they hire candidates with the right skillset so their team can be successful. Although engineers will always learn on the job, having a solid foundation from the start is very important. For example, if your company primarily uses Apache Airflow, you should not hire someone that does not know python. There is always a learning curve when a new employee comes on board, but learning the use-case vs learning the entire technology are two very different things. Modern data teams are responsible for mission critical tasks and analysis that can change the course of a company, and having professionals on-hand that are experienced in your companies data tools can be a major advantage. The most effective way to find candidates with the right skills is to use job postings and other recruitment methods specifically tailored to finding talent with the specific skills you need.</p><h3>Assessing their Technical Capabilities</h3><p>When hiring a new data team member, it is important to assess their technical capabilities in order to ensure you are getting the right person for the job. This requires careful evaluation of the candidate’s skill set and experience with relevant technologies. A good way to get an idea of a candidate’s technical skills is by asking them specific questions about their experience with different technologies or giving them sample problems that require some level of coding or analysis. Many times the only way to truly assess someones ability is a live test, as take home tests are frequently completed by someone else. Beyond the technology, it is also important to evaluate how they approach problem-solving and troubleshooting tasks related to data related tasks. Lastly, references from past employers can provide helpful insight into the abilities of potential candidates. Ultimately, how you assess the ability of a new candidate may vary depending on your specific needs, but assessing a candidate’s technical capabilities before hiring them will help make sure your new team member has all the necessary skills needed for successful employment.</p><h3>Ensuring They Fit Well into your Company Culture</h3><p>When hiring new data team members, it is essential to ensure that they fit well into your company culture. This is because the proper implementation of data projects usually requires collaboration and communication between a variety of teams. Data teams are the heart of any data driven organization and rarely reside in a silo. The average data team may work with team members from Devops, Product Engineering, Product Management, Finance, etc. Data teams typically work with lots of people with different skillsets and backgrounds, making a shared understanding of the company’s vision, goals and values vital for success. When data teams are well-aligned with the company’s culture and people, they can help foster an environment of understanding and trust in the data.</p><h3>Don’t Forget Soft Skills</h3><p>Many times the interview process for analysts and engineers focus heavily on technical aspects, but successful data teams require a unique combination of technical and non-technical skills. Both are necessary to ensure the accuracy of data and the happiness of stakeholders. Team members need strong soft skills to build relationships across different departments, and it’s important that all data team members possess the soft skills needed to effectively work with their team members, as well as with other teams in the company. This will not only allow your data team to be successful, but can also help facilitate trust in the data they provide; something that is a common challenge in data driven companies with self-serve analytics.</p><h3>Conclusion</h3><p>After reading this blog post I hope you have a better understanding of how to successfully hire a new member of your data team. While these steps may seem simple, implementing them can be difficult. As always, hiring and retaining talent can be hard- if you need help finding new members for your team reach out to us at <a href="http://pivotcomputing.io/">Pivot Computing</a>. We are happy to help.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80ba3ace40b9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pros and Cons of Using Persistent Derived Tables (PDTs) in Looker]]></title>
            <link>https://eric-arsenaults.medium.com/pros-and-cons-of-using-persistent-derived-tables-pdts-in-looker-1ea0112307b1?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ea0112307b1</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[dbt]]></category>
            <category><![CDATA[looker]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Sun, 14 May 2023 18:02:02 GMT</pubDate>
            <atom:updated>2023-05-15T04:28:44.500Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/600/0*7KfFzwW9PT01rFPL.png" /></figure><p>Looker is a powerful analytics platform that allows users to quickly and easily explore data, build complex visualizations and dashboards, and uncover insights. Using LookML, the underlying modeling language of Looker, users can define their data models and create custom views for exploring their data. One of the most powerful feature of LookML is Persistent Derived Tables (PDTs), which allow users to store pre-calculated results in database tables, making it easier to query large datasets. In this blog post, we will take a closer look at PDTs in Looker and discuss the pros and cons of using them within your organization’s data stack.</p><h3>Pros:</h3><p>The primary advantage of using PDTs is that they allow for much more efficient data retrieval. By persisting results and storing them in a database table, users are able to access the information much faster than they would with a traditional LookML model. There is no need to perform calculations each time a query is made, making individual queries much faster. This speeds up performance significantly and ensures Looker users can gain access to the data they need quickly and efficiently.</p><p>PDTs also allow for better scalability of large datasets, making it easier to query data across multiple sources. This is especially useful if you’re dealing with a high volume of data as PDTs make speedier queries possible without sacrificing accuracy or quality.</p><p>PDTs can also be setup with custom datagroups, which can help keep costs down. Instead of relying on a manual or timed trigger, Looker will trigger builds when underlying data sources change. Users also don’t need to setup complicated sensors, as each datagroup takes just one SQL query as its input. This means that users can have confidence in their PDTs without needing to check underlying data sources or worry about timing.</p><p>Lastly, PDTs are helpful because they are created in the Looker UI but persists in your database and only work in Looker. This means that you can give your BI analyst team access to build tables while still keeping them behind the safeguard of the Looker UI. You can allow them to model data and persist tables without giving them access to production data pipelines. This enables self serve analytics for the team while still maintaining good security for the whole organization.</p><h3>Cons:</h3><p>However, there are some drawbacks to using PDTs in Looker. One of the main drawbacks is the cost associated with setting up and maintaining them. Additional storage space is used in the organizations warehouse to write the tables which costs money. They must also be maintained in the case that the underlying data changes or anything breaks, and can cause a good bit of waste when they are broken. When a PDT is broken it will continue to spin up a failed query every time your datagroup cron checker goes off (default is every 5 mins). PTDs can be expensive if you are not prepared to maintain them.</p><p>Another downside is that it requires extra effort to maintain the LookML view. If a new column is added or an existing column is modified, the user must manually update the view LookML in Looker. This means that if you are using a large number of columns or tables, or data that frequently changes, it can be quite time consuming to keep up with all the changes. The risk of overlooking something important increases.</p><p>Another downside is that PDTs can not be easily queried outside of Looker. Although this was one of the Pros that was mentioned earlier, it also is a Con in some respects. Since the table names are pre-pended with a string of numbers that change each time the table is re-written, PDTs can not be used with any platform other than Looker. This is very limiting; the organization is paying for a table that can only be used by one of the available data assets.</p><p>Additionally, relying on this approach may slow down query performance in some cases as PDTs rely on joins between tables. When querying derived tables, Looker must perform a join on each row of data and then filter the results to return the desired output. This can significantly affect query performance if you are dealing with large datasets or complex queries. PDTs also get very slow and almost un-usable when they are built on top of each other in a cascading fashion similar to a DAG. PDTs are a good tool for quick BI modeling but should not be the singular tool for data modeling at an organization.</p><p>Lastly, this approach isn’t suitable for all types of data. If your dataset contains time-series data, for example, a materialized view might be more efficient. Materialized views stored in the database and can queried directly by Looker reducing query latency and improving performance without the need for PDTs.</p><h3>Conclusion:</h3><p>Overall, persistent derived tables provide valuable benefits in terms of scalability and query speed when used properly, but not without their downsides. PTDs also can be costly and slow if implemented wrong, and can be limiting to the organization as a whole. With careful consideration of the pros and cons, you can decide if using a PDTs is the best option for your business needs.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ea0112307b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Using Exposures in dbt Core: Define Downstream Uses]]></title>
            <link>https://eric-arsenaults.medium.com/using-exposures-in-dbt-define-downstream-uses-a6992ec206c?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6992ec206c</guid>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[dbt]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-visualization]]></category>
            <category><![CDATA[data-analysis]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Sun, 14 May 2023 16:29:08 GMT</pubDate>
            <atom:updated>2023-05-31T18:19:45.381Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wDu1cFRf78hPmCpo.jpg" /></figure><h3>Overview of dbt Core and Exposures</h3><p>dbt Core is an open source command line interface (CLI) that helps users to quickly define, build, and deploy data pipelines. It also supports a feature called Exposures which allows developers to easily categorize their models with minimal effort. With the Exposure feature, users can define downstream uses in YAML files that are nested under an ‘exposures’ key. These files can be named whatever you want (snake_case only) and stored anywhere within the models directory. Exposures can be used to define downstream uses for each model, making them callable at runtime. This makes it easier for developers to make changes to specific model groups when updating existing datasets or creating new ones. Additionally, exposures provide a way to for developers to choose which downstream project they want to refresh at runtime, saving time and resources.</p><p>In short, using exposures provides a number of significant advantages. By allowing developers to define, select, and run specific groups of models at runtime, they gain a greater level of modularity over their project.</p><h3>Understanding Different Types of Exposures</h3><p>When creating exposures in dbt Core users have the option to choose from a variety of available properties, but only three are required (Name, Type, Owner). All of these properties as a whole can be used to customize the exposure and determine which downstream projects will be affected by it. Some of the other key options include the description, tags, maturity, metadata and even a url to link directly to the downstream use case. By selecting these properties carefully, developers are able to create custom exposures that provide more control over their project’s modularity and flexibility.</p><p>Here is a breakdown of the Available Properties:</p><h4>Available properties<a href="https://docs.getdbt.com/docs/build/exposures#available-properties">​</a></h4><p><em>Required:</em></p><ul><li>name: a unique exposure name written in <a href="https://en.wikipedia.org/wiki/Snake_case">snake case</a></li><li>type: one of dashboard, notebook, analysis, ml, application (used to organize in docs site)</li><li>owner: name or email required; additional properties allowed</li></ul><p><em>Expected:</em></p><ul><li>depends_on: list of refable nodes, including ref, source, and metric (While possible, it is highly unlikely you will ever need an exposure to depend on a source directly)</li></ul><p><em>Optional:</em></p><ul><li>label: may contain spaces, capital letters, or special characters.</li><li>url: enables the link to View this exposure in the upper right corner of the generated documentation site</li><li>maturity: one of high, medium, low</li></ul><p><em>General properties (optional)</em></p><ul><li>description</li><li>tags</li><li>meta</li></ul><h4>Referencing exposures​</h4><p>Once an exposure is defined, you can run commands that reference it:</p><pre>dbt run -s +exposure:finance_dashboards<br>dbt test -s +exposure:finance_dashboards</pre><h3>Final Thoughts on Utilizing Exposures</h3><p>Exposures can be a powerful tool for analytics engineers to organize their project and define downstream uses. With exposures, you can create a project that is organized according to different groups of usage, provide labels and URLs so the exposure is easy to find, set maturity ratings on each exposure item, add descriptions, tags and meta data which will help with searching through your codebase more efficiently. All these features make Exposures an invaluable asset when it comes to organizing your project. By taking advantage of this feature within dbt Core, analytics engineers can quickly find what they need while also ensuring that their projects are flexible and modular.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6992ec206c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introduction to Testing in dbt (Data Build Tool)]]></title>
            <link>https://eric-arsenaults.medium.com/introduction-to-testing-in-dbt-data-build-tool-451a084d7798?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/451a084d7798</guid>
            <category><![CDATA[dbt]]></category>
            <category><![CDATA[data-science]]></category>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[business-intelligence]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Sun, 14 May 2023 05:47:37 GMT</pubDate>
            <atom:updated>2023-07-12T18:31:03.667Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction to Testing in dbt Core</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*eI8k0IAzYQ4Vns5C" /></figure><h3>What is dbt Core and Why You Should Add it to Your Data Stack</h3><p>dbt Core is an open-source data engineering framework used to automate the process of transforming data from raw sources into analytics-ready models. It provides a unified interface for developing and managing data pipelines, as well as reducing the time and complexity associated with building analytics solutions. dbt Core’s unique architecture combines SQL and Jinja templating to provide highly modularized, extensible, and easily maintainable code. Testing is a critical part of the data engineering workflow, as it helps ensure that resulting models are accurate and reliable. dbt Core provides several features designed to make testing easier, including assertions and test suites.</p><h3>The Basics of dbt Core Testing: Types of Tests</h3><p>dbt Core provides a comprehensive suite of tests to help ensure that data models and pipelines are accurate and reliable. Tests can be divided into two main categories: structural tests and semantic tests. Structural tests check the physical structure of a model, such as whether columns are present or absent, while semantic tests check the logical structure of the model, such as whether calculation logic is implemented correctly. Assertions are a type of structural test that checks the data against expected values. These tests can be used to check properties of individual datasets, such as checking if a column has the correct data type or contains specific values.</p><h3>Setting Up a Testing Environment for dbt Core</h3><p>Setting up a testing environment for dbt Core is an important step in ensuring data quality and accuracy. As mentioned testing involves running two main categories of tests: structural tests, which check the physical structure of a model, and semantic tests, which check the logical structure. Test suites allow multiple assertions to be grouped together and run in sequence to facilitate more comprehensive testing. Additionally, it is beneficial to set up automated processes so that any changes or updates made in the database are tested automatically when they occur. By setting up an appropriate testing environment for dbt Core, users can ensure their data remains accurate and reliable over time.</p><p>Automated processes are especially important for ensuring the timeliness of tests. Using dbt Core, users can set up jobs that run on a recurring schedule to check for any changes or updates made in the database and perform the necessary tests. These automated tests can also be used to check incoming data, as well as to checking for any discrepancies or errors.</p><h3>Best Practices for Writing Tests in dbt Core</h3><p>When writing tests in dbt Core, it is important to ensure that they are comprehensive, accurate and reliable. As such, best practices include defining test scenarios in detail and ensuring that the test covers all possible functions of the database. Additionally, it is important to keep tests up-to-date and ensure that any changes are tested against the existing tests.</p><p>It is also important that test results are reported accurately and communicated using some form of alerting so that any issues or discrepancies can be identified quickly. Additionally, it is important to ensure all tests are written in a way that makes them easy to understand and debug, as this will help to simplify the process of resolving any issues. Finally, automated testing is also recommended, as it can save a lot of time and effort in the long run.</p><p>Overall, dbt Core testing is an essential part of ensuring that any changes or improvements to the project do not result in unexpected consequences for downstream users. By following best practices and using the right tools, it is possible to ensure that all necessary tests are performed and any issues are identified quickly and fixed swiftly. Doing so will help keep the data stack running smoothly and efficiently, providing stakeholders with a great experience.</p><h3>Troubleshooting Common Issues With Tests</h3><p>Troubleshooting common issues when running tests in dbt Core can be a difficult task, especially if you don’t have the right tools or experience. It’s important to understand the fundamentals of dbt Core and how it works so that you can effectively identify any issues. The first step is to confirm that all data sources are connected properly and that all models are populated with data. Next, check for any errors or warnings in the output logs that may indicate a problem. If needed, you can also check your run_results.json file after the run. Finally, use debugging tools such as the <a href="https://marketplace.visualstudio.com/items?itemName=bastienboutonnet.vscode-dbt">VS Code plugin</a> to investigate any issues further and find solutions. Learning how to write custom tests in SQL can help you quickly identify problems and take corrective action. With the right understanding of dbt Core and the right tools, you can ensure that your data models are performing as expected.</p><h3>Tips for Effective Test Suites with dbt Core</h3><p>Creating effective test suites with dbt Core requires a combination of best practices and advanced features. First, determine the scope of your tests and decide which data sources and models you want to validate. Try to cover every possible test case that could result in errors or incorrect data. Once you have identified all applicable tests, create custom SQL queries for each to validate the model. If needed, try to isolate and work around edge cases.</p><p>dbt Core provides a suite of advanced features to help you create robust tests, such as data snapshots and automated testing. Data snapshots allow you to compare the results of two runs over time to check for any unexpected changes in output. Automated testing lets you run regression tests on multiple models or sources concurrently and generate reports with any discrepancies.</p><p>By using dbt Core to validate data sources and models, you can be sure that your analytics are accurate and reliable. With automated testing, you can quickly identify potential issues before they impact analytical processes and flow through to stake holders. And with data snapshots, you can track changes over time to ensure that processes remain consistent. By leveraging these features, organizations can gain confidence in their data that spreads across the entire company.</p><h3>Conclusion:</h3><p>Analytics engineers should consider leveraging the powerful features of dbt Core to ensure their analytics are accurate and reliable. Automated testing allows for quick identification of potential issues, while data snapshots provide a way to track changes over time. With these tools at your disposal, you can rest assured that all processes remain consistent and any discrepancies will be quickly identified. By utilizing dbt Core’s automated testing capabilities, organizations can gain greater confidence in their data-driven decision making process with fewer resources expended on manual validation tasks. This enables organizations to accurately monitor the performance of their systems in order to respond quickly and appropriately to any changes that occur. By leveraging dbt Core’s automated testing capabilities, data engineers can ensure that their analytics are accurate and reliable, allowing stake holders to make informed decisions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=451a084d7798" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Free Monitoring Dashboard for Looker]]></title>
            <link>https://eric-arsenaults.medium.com/my-gift-to-you-a-free-monitoring-dashboard-for-looker-759cc5fb232b?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/759cc5fb232b</guid>
            <category><![CDATA[data-engineering]]></category>
            <category><![CDATA[analytics-engineering]]></category>
            <category><![CDATA[looker]]></category>
            <category><![CDATA[data-analysis]]></category>
            <category><![CDATA[analytics]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Tue, 04 Apr 2023 19:04:31 GMT</pubDate>
            <atom:updated>2023-07-12T18:31:43.163Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tJOWCIoEfNRSPSnz.jpg" /></figure><p>I have worked a lot of consulting and data team jobs in recent years and have found a lot of success in managing Looker environments. At this point I have worked on a lot of environments; somewhere in the neighborhood of 20–25 (but who’s counting 😃). Anyone that has worked as a Looker admin can vouch; Looker environments can get out of control QUICK if you are not monitoring them closely. Looker comes stock with a few dashboards for this purpose that are pretty helpful, but I have always found that I prefer to have one central dash that I can check each day to make sure everything is running smoothly. Over the years I have built this dashboard; some of it is ripped off the Looker provided dashboards, and some I have created myself. Either way, I have used this dashboard at many companies with great success. Since the Looker metadata explores are the same across all Looker instances, there is nothing proprietary or unethical about sharing the LookML code. For this reason, I have decided to give this away for free. To be honest, a dashboard like this is just the tip of the iceberg when it comes to keeping a Looker environment running smoothly.</p><p>Without further ado, here is the dashboard LookML. The colors may get messed up depending on how you have setup your default settings, and you may want to apply some more filters depending on the specifics of your instance, but the idea is the same. Just add this as a .dashboard file and “include:” the file in one of your models and it will pop up in your LookML Dashboard folder.</p><pre>- dashboard: environment_performance_dashboard<br>  title: Environment Performance Dashboard<br>  layout: newspaper<br>  preferred_viewer: dashboards-next<br>  description: &#39;&#39;<br>  preferred_slug: qo4RsUk7JZW040IYxsMRAq<br>  elements:<br>  - title: Runtime Run Count and Query Count by Dashboard L30D<br>    name: Runtime Run Count and Query Count by Dashboard L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_column<br>    fields: [dashboard.title, history.average_runtime, history.dashboard_run_count,<br>      history.query_run_count]<br>    filters:<br>      history.completed_date: 30 days<br>    sorts: [history.average_runtime desc]<br>    limit: 100<br>    column_limit: 50<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: circle<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    y_axes: [{label: !!null &#39;&#39;, orientation: left, series: [{axisId: history.average_runtime,<br>            id: history.average_runtime, name: Average Runtime in Seconds}], showLabels: false,<br>        showValues: true, unpinAxis: true, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: !!null &#39;&#39;, orientation: right, series: [{axisId: history.dashboard_run_count,<br>            id: history.dashboard_run_count, name: Dashboard Run Count}], showLabels: false,<br>        showValues: false, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: !!null &#39;&#39;, orientation: right, series: [{axisId: history.query_run_count,<br>            id: history.query_run_count, name: Query Run Count}], showLabels: false,<br>        showValues: false, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}]<br>    series_types:<br>      history.query_run_count: scatter<br>      history.dashboard_run_count: scatter<br>    series_colors:<br>      history.average_runtime: &quot;#2C72AC&quot;<br>      history.dashboard_run_count: &quot;#222&quot;<br>      query.count: &quot;#2C72AC&quot;<br>      history.query_run_count: &quot;#F88017&quot;<br>    series_labels: {}<br>    reference_lines: [{reference_type: line, line_value: &#39;30&#39;, range_start: max, range_end: min,<br>        margin_top: deviation, margin_value: mean, margin_bottom: deviation, label_position: right,<br>        color: &quot;#B32F37&quot;, label: 30 Seconds}]<br>    trend_lines: []<br>    swap_axes: false<br>    show_null_points: true<br>    defaults_version: 1<br>    interpolation: linear<br>    hidden_fields: []<br>    hidden_points_if_no: []<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    listen: {}<br>    row: 89<br>    col: 0<br>    width: 24<br>    height: 11<br>  - title: Runs by Looker Node L30D<br>    name: Runs by Looker Node L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_column<br>    fields: [history.average_runtime, history.dashboard_run_count, node.id, node.hostname,<br>      node.is_master, node.port, node.version]<br>    filters:<br>      history.completed_date: 30 days<br>    sorts: [history.dashboard_run_count desc]<br>    limit: 100<br>    column_limit: 50<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: circle<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    y_axes: [{label: !!null &#39;&#39;, orientation: left, series: [{axisId: history.average_runtime,<br>            id: history.average_runtime, name: Average Runtime in Seconds}], showLabels: true,<br>        showValues: true, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: !!null &#39;&#39;, orientation: right, series: [{axisId: history.dashboard_run_count,<br>            id: history.dashboard_run_count, name: Dashboard Run Count}], showLabels: true,<br>        showValues: true, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}]<br>    series_types:<br>      history.average_runtime: scatter<br>    series_colors:<br>      history.average_runtime: &quot;#222&quot;<br>      history.dashboard_run_count: &quot;#2C72AC&quot;<br>    series_labels: {}<br>    reference_lines: [{reference_type: line, line_value: &#39;30&#39;, range_start: max, range_end: min,<br>        margin_top: deviation, margin_value: mean, margin_bottom: deviation, label_position: right,<br>        color: &quot;#B32F37&quot;, label: 30 Seconds}]<br>    trend_lines: []<br>    swap_axes: false<br>    show_null_points: true<br>    defaults_version: 1<br>    interpolation: linear<br>    hidden_fields: [node.hostname, node.is_master, node.port]<br>    hidden_points_if_no: []<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    listen: {}<br>    row: 132<br>    col: 0<br>    width: 24<br>    height: 7<br>  - title: Cache vs Database Drill L30D<br>    name: Cache vs Database Drill L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_grid<br>    fields: [dashboard.title, history.average_runtime, history.dashboard_run_count,<br>      query.count, history.result_source]<br>    pivots: [history.result_source]<br>    filters:<br>      history.completed_date: 30 days<br>      history.result_source: -&quot;stale_cache&quot;,-EMPTY<br>    sorts: [history.result_source desc, avg_runtime_seconds desc 0]<br>    limit: 100<br>    column_limit: 50<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.average_runtime}&quot;,<br>        label: AVG Runtime Seconds, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: avg_runtime_seconds, _type_hint: number}]<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, dashboard.title, query_avg_runtime_seconds,<br>      query_history.dashboard_run_count, query_query.count, cache_avg_runtime_seconds,<br>      cache_history.dashboard_run_count, cache_query.count]<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      query.count: Query Count<br>    series_column_widths:<br>      avg_runtime_seconds: 112<br>    series_cell_visualizations:<br>      history.average_runtime:<br>        is_active: false<br>    series_text_format:<br>      query.count:<br>        align: left<br>      history.dashboard_run_count:<br>        align: left<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: circle<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    y_axes: [{label: !!null &#39;&#39;, orientation: left, series: [{axisId: history.average_runtime,<br>            id: history.average_runtime, name: Average Runtime in Seconds}], showLabels: true,<br>        showValues: true, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: &#39;&#39;, orientation: right, series: [{axisId: query.count,<br>            id: query.count, name: Query}], showLabels: true, showValues: true, unpinAxis: false,<br>        tickDensity: default, type: linear}]<br>    series_types: {}<br>    series_colors:<br>      history.average_runtime: &quot;#222&quot;<br>      history.dashboard_run_count: &quot;#2C72AC&quot;<br>      query.count: &quot;#2C72AC&quot;<br>    reference_lines: [{reference_type: line, line_value: &#39;30&#39;, range_start: max, range_end: min,<br>        margin_top: deviation, margin_value: mean, margin_bottom: deviation, label_position: right,<br>        color: &quot;#B32F37&quot;, label: 30 Seconds}]<br>    trend_lines: []<br>    swap_axes: false<br>    show_null_points: true<br>    defaults_version: 1<br>    interpolation: linear<br>    hidden_fields: [history.average_runtime]<br>    hidden_points_if_no: []<br>    pinned_columns:<br>      &quot;$$$_row_numbers_$$$&quot;: left<br>      dashboard.title: left<br>    listen: {}<br>    row: 109<br>    col: 0<br>    width: 24<br>    height: 9<br>  - title: Scheduled Plan Count (Dashboards)<br>    name: Scheduled Plan Count (Dashboards)<br>    model: system__activity<br>    explore: scheduled_plan<br>    type: looker_grid<br>    fields: [dashboard.title, count_of_id_2, count_of_user_id, count_of_address, dashboard.id]<br>    filters:<br>      dashboard.title: &quot;-NULL&quot;<br>    sorts: [count_of_id_2 desc]<br>    limit: 500<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${count_of_id_2}&quot;,<br>        label: Schedule Count, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: schedule_count, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_user_id}&quot;, label: Count<br>          of Users (Scheduler), value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: measure, table_calculation: count_of_users_scheduler, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_address}&quot;, label: Recipient<br>          Count, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        table_calculation: recipient_count, _type_hint: number}, {measure: count_of_id,<br>        based_on: scheduled_job.id, expression: &#39;&#39;, label: Count of ID, type: count_distinct,<br>        _kind_hint: measure, _type_hint: number}, {category: measure, expression: &#39;&#39;,<br>        label: Count of User ID, based_on: scheduled_plan.user_id, _kind_hint: measure,<br>        measure: count_of_user_id, type: count_distinct, _type_hint: number}, {measure: count_of_address,<br>        based_on: scheduled_plan_destination.address, expression: &#39;&#39;, label: Count<br>          of Address, type: count_distinct, _kind_hint: measure, _type_hint: number},<br>      {measure: count_of_id_2, based_on: scheduled_plan.id, expression: &#39;&#39;, label: Count<br>          of ID, type: count_distinct, _kind_hint: measure, _type_hint: number}]<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, dashboard.title, dashboard.id, schedule_count,<br>      count_of_users_scheduler, recipient_count, scheduled_job_stage.avg_runtime]<br>    show_totals: true<br>    show_row_totals: true<br>    series_cell_visualizations:<br>      count_of_id:<br>        is_active: false<br>        palette:<br>          palette_id: 1e4d66b9-f066-4c33-b0b7-cc10b4810688<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    series_text_format:<br>      recipient_count:<br>        align: left<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    series_types: {}<br>    hidden_fields: [count_of_user_id, count_of_address, count_of_id_2, dashboard.id]<br>    y_axes: []<br>    listen: {}<br>    row: 118<br>    col: 0<br>    width: 24<br>    height: 6<br>  - title: Cache vs Database L30D<br>    name: Cache vs Database L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_column<br>    fields: [dashboard.title, history.cache_result_query_count, history.database_result_query_count,<br>      history.query_run_count]<br>    filters:<br>      history.completed_date: 30 days<br>      dashboard.title: &quot;-EMPTY&quot;<br>    sorts: [sort desc]<br>    limit: 500<br>    column_limit: 50<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.cache_result_query_count}\n\<br>          \n/\n\n(${history.database_result_query_count}\n+ \n${history.cache_result_query_count})&quot;,<br>        label: sort, value_format: !!null &#39;&#39;, value_format_name: percent_0, _kind_hint: measure,<br>        table_calculation: sort, _type_hint: number}]<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: percent<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: circle<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    y_axes: [{label: !!null &#39;&#39;, orientation: left, series: [{axisId: history.average_runtime,<br>            id: history.average_runtime, name: Average Runtime in Seconds}], showLabels: true,<br>        showValues: true, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: &#39;&#39;, orientation: right, series: [{axisId: query.count,<br>            id: query.count, name: Query}], showLabels: true, showValues: true, unpinAxis: false,<br>        tickDensity: default, type: linear}]<br>    hidden_series: [history.dashboard_run_count, query.count]<br>    series_types:<br>      history.average_runtime: scatter<br>    series_colors:<br>      history.average_runtime: &quot;#222&quot;<br>      history.dashboard_run_count: &quot;#2C72AC&quot;<br>      query.count: &quot;#2C72AC&quot;<br>      history.database_result_query_count: &quot;#2C72AC&quot;<br>      history.cache_result_query_count: &quot;#222&quot;<br>    series_labels: {}<br>    reference_lines: [{reference_type: line, line_value: &#39;30&#39;, range_start: max, range_end: min,<br>        margin_top: deviation, margin_value: mean, margin_bottom: deviation, label_position: right,<br>        color: &quot;#B32F37&quot;, label: 30 Seconds}]<br>    trend_lines: []<br>    swap_axes: false<br>    show_null_points: true<br>    defaults_version: 1<br>    interpolation: linear<br>    hidden_fields: [history.query_run_count, sort]<br>    hidden_points_if_no: []<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    listen: {}<br>    row: 100<br>    col: 0<br>    width: 24<br>    height: 9<br>  - name: Performance and Users<br>    type: text<br>    title_text: Performance and Users<br>    body_text: &#39;&#39;<br>    row: 0<br>    col: 0<br>    width: 24<br>    height: 2<br>  - name: Dashboards and Schedules<br>    type: text<br>    title_text: Dashboards and Schedules<br>    body_text: &#39;&#39;<br>    row: 87<br>    col: 0<br>    width: 24<br>    height: 2<br>  - title: Query Times by Source L30D<br>    name: Query Times by Source L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_bar<br>    fields: [history.issuer_source, history.query_run_count, history.runtime_tiers]<br>    pivots: [history.runtime_tiers]<br>    filters:<br>      history.completed_date: 30 days<br>      history.runtime_tiers: &quot;-Below 0, -Undefined&quot;<br>      history.issuer_source: &quot;-API,-Action Hub,-Other&quot;<br>    sorts: [history.runtime_tiers, history.issuer_source desc]<br>    limit: 500<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: normal<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: 5591d8d1-6b49-4f8e-bafa-b874d82f8eb7<br>      palette_id: 57bef7ef-25c4-448e-83df-9c4de399305d<br>      options:<br>        steps: 5<br>        reverse: true<br>    y_axes: []<br>    font_size: &#39;12&#39;<br>    series_types: {}<br>    series_colors: {}<br>    charts_across: 4<br>    defaults_version: 1<br>    value_labels: legend<br>    label_type: labPer<br>    hidden_fields: []<br>    listen: {}<br>    row: 40<br>    col: 0<br>    width: 12<br>    height: 8<br>  - title: New Tile<br>    name: New Tile<br>    model: system__activity<br>    explore: user<br>    type: single_value<br>    fields: [user.count]<br>    filters:<br>      user.is_disabled: &#39;No&#39;<br>      user_facts.is_looker_employee: &#39;No&#39;<br>    limit: 500<br>    dynamic_fields: [{category: table_calculation, expression: &#39;running_total(${user.count})&#39;,<br>        label: Total Users, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: total_users, _type_hint: number, is_disabled: true}]<br>    query_timezone: America/Denver<br>    custom_color_enabled: true<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: value<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    enable_conditional_formatting: false<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    single_value_title: Total Users<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: true<br>    interpolation: linear<br>    series_colors:<br>      user.count: &quot;#2C72AC&quot;<br>      session.count: &quot;#222&quot;<br>    defaults_version: 1<br>    hidden_fields: []<br>    series_types: {}<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    y_axes: []<br>    listen: {}<br>    row: 2<br>    col: 0<br>    width: 5<br>    height: 4<br>  - title: Top Users L30D<br>    name: Top Users L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_grid<br>    fields: [history.dashboard_run_count, user.name, query.count]<br>    filters:<br>      history.completed_month: 30 days<br>    sorts: [query.count desc]<br>    limit: 500<br>    column_limit: 50<br>    query_timezone: America/Denver<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    truncate_header: false<br>    series_cell_visualizations:<br>      history.dashboard_run_count:<br>        is_active: true<br>        palette:<br>          palette_id: 85de97da-2ded-4dec-9dbd-e6a7d36d5825<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>      query.count:<br>        is_active: true<br>    custom_color_enabled: true<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: value<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: true<br>    interpolation: linear<br>    defaults_version: 1<br>    hidden_fields: [history.dashboard_run_count]<br>    series_types: {}<br>    y_axes: []<br>    listen: {}<br>    row: 32<br>    col: 12<br>    width: 12<br>    height: 8<br>  - title: Dashboard Runs L30D<br>    name: Dashboard Runs L30D<br>    model: system__activity<br>    explore: history<br>    type: single_value<br>    fields: [history.dashboard_run_count]<br>    filters:<br>      history.completed_month: 30 days<br>    sorts: [history.dashboard_run_count desc]<br>    limit: 500<br>    query_timezone: America/Denver<br>    custom_color_enabled: true<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: value<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    enable_conditional_formatting: false<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_cell_visualizations:<br>      history.dashboard_run_count:<br>        is_active: true<br>        palette:<br>          palette_id: 85de97da-2ded-4dec-9dbd-e6a7d36d5825<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: true<br>    interpolation: linear<br>    defaults_version: 1<br>    hidden_fields: []<br>    series_types: {}<br>    y_axes: []<br>    listen: {}<br>    row: 2<br>    col: 10<br>    width: 5<br>    height: 4<br>  - title: Query Runs L30D<br>    name: Query Runs L30D<br>    model: system__activity<br>    explore: history<br>    type: single_value<br>    fields: [history.query_run_count]<br>    filters:<br>      history.completed_month: 30 days<br>    limit: 500<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.query_run_count}&quot;,<br>        label: &#39;Query Runs &#39;, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: query_runs, _type_hint: number}]<br>    query_timezone: America/Denver<br>    custom_color_enabled: true<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: value<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    enable_conditional_formatting: false<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: bergfreunde_bw<br>      palette_id: bergfreunde_bw-categorical-0<br>      options:<br>        steps: 5<br>    custom_color: &quot;#000000&quot;<br>    conditional_formatting: []<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    series_types: {}<br>    point_style: circle<br>    series_colors:<br>      history.query_run_count: &quot;#222&quot;<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: true<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_cell_visualizations:<br>      history.dashboard_run_count:<br>        is_active: true<br>        palette:<br>          palette_id: 85de97da-2ded-4dec-9dbd-e6a7d36d5825<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    interpolation: linear<br>    defaults_version: 1<br>    hidden_fields: [history.query_run_count]<br>    map_plot_mode: points<br>    heatmap_gridlines: false<br>    heatmap_gridlines_empty: false<br>    heatmap_opacity: 0.5<br>    show_region_field: true<br>    draw_map_labels_above_data: true<br>    map_tile_provider: light<br>    map_position: fit_data<br>    map_scale_indicator: &#39;off&#39;<br>    map_pannable: true<br>    map_zoomable: true<br>    map_marker_type: circle<br>    map_marker_icon_name: default<br>    map_marker_radius_mode: proportional_value<br>    map_marker_units: meters<br>    map_marker_proportional_scale_type: linear<br>    map_marker_color_mode: fixed<br>    show_legend: true<br>    quantize_map_value_colors: false<br>    reverse_map_value_colors: false<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    y_axes: []<br>    listen: {}<br>    row: 2<br>    col: 15<br>    width: 5<br>    height: 4<br>  - title: Runtime<br>    name: Runtime<br>    model: system__activity<br>    explore: history<br>    type: single_value<br>    fields: [history.average_runtime]<br>    filters:<br>      history.completed_date: 30 days<br>    limit: 500<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.average_runtime}&quot;,<br>        label: avg, value_format: !!null &#39;&#39;, value_format_name: decimal_1, _kind_hint: measure,<br>        table_calculation: avg, _type_hint: number}]<br>    query_timezone: America/Denver<br>    custom_color_enabled: true<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: value<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    enable_conditional_formatting: false<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: bergfreunde_2<br>      palette_id: bergfreunde_2-categorical-0<br>      options:<br>        steps: 5<br>    single_value_title: Average Runtime Seconds L30D<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: normal<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    font_size: &#39;12&#39;<br>    series_types: {}<br>    series_colors: {}<br>    charts_across: 4<br>    defaults_version: 1<br>    value_labels: legend<br>    label_type: labPer<br>    hidden_fields: [history.average_runtime]<br>    y_axes: []<br>    listen: {}<br>    row: 2<br>    col: 20<br>    width: 4<br>    height: 4<br>  - title: &#39;Query Runs: Cache vs Database L3M&#39;<br>    name: &#39;Query Runs: Cache vs Database L3M&#39;<br>    model: system__activity<br>    explore: history<br>    type: looker_column<br>    fields: [history.average_runtime, history.dashboard_run_count, query.count, history.result_source,<br>      history.completed_week]<br>    pivots: [history.result_source]<br>    fill_fields: [history.completed_week]<br>    filters:<br>      history.result_source: -&quot;stale_cache&quot;,-EMPTY<br>      history.completed_month: 3 months<br>    sorts: [history.result_source desc, history.completed_week desc]<br>    limit: 100<br>    column_limit: 50<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.average_runtime}&quot;,<br>        label: AVG Runtime Seconds, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: avg_runtime_seconds, _type_hint: number}]<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: normal<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: circle<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    y_axes: [{label: !!null &#39;&#39;, orientation: left, series: [{axisId: history.average_runtime,<br>            id: history.average_runtime, name: Average Runtime in Seconds}], showLabels: true,<br>        showValues: true, unpinAxis: false, tickDensity: default, tickDensityCustom: 5,<br>        type: linear}, {label: &#39;&#39;, orientation: right, series: [{axisId: query.count,<br>            id: query.count, name: Query}], showLabels: true, showValues: true, unpinAxis: false,<br>        tickDensity: default, type: linear}]<br>    series_types: {}<br>    series_colors:<br>      history.average_runtime: &quot;#222&quot;<br>      history.dashboard_run_count: &quot;#2C72AC&quot;<br>      query.count: &quot;#2C72AC&quot;<br>      query - query.count: &quot;#222&quot;<br>      cache - query.count: &quot;#2C72AC&quot;<br>    series_labels:<br>      query.count: Query Count<br>      query - query.count: Results from Database<br>      cache - query.count: Results from Cache<br>    reference_lines: []<br>    trend_lines: []<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, dashboard.title, query_avg_runtime_seconds,<br>      query_history.dashboard_run_count, query_query.count, cache_avg_runtime_seconds,<br>      cache_history.dashboard_run_count, cache_query.count]<br>    show_totals: true<br>    show_row_totals: true<br>    series_column_widths:<br>      avg_runtime_seconds: 112<br>    series_cell_visualizations:<br>      history.average_runtime:<br>        is_active: false<br>    series_text_format:<br>      query.count:<br>        align: left<br>      history.dashboard_run_count:<br>        align: left<br>    swap_axes: false<br>    show_null_points: true<br>    defaults_version: 1<br>    interpolation: linear<br>    hidden_fields: [history.average_runtime, avg_runtime_seconds, history.dashboard_run_count]<br>    hidden_points_if_no: []<br>    pinned_columns:<br>      &quot;$$$_row_numbers_$$$&quot;: left<br>      dashboard.title: left<br>    listen: {}<br>    row: 14<br>    col: 0<br>    width: 24<br>    height: 9<br>  - name: Query Runs vs Runtime L3M<br>    title: Query Runs vs Runtime L3M<br>    merged_queries:<br>    - model: system__activity<br>      explore: user<br>      type: table<br>      fields: [user.count, user.created_week]<br>      fill_fields: [user.created_week]<br>      filters:<br>        user.is_disabled: &#39;No&#39;<br>        user.created_month: 3 months<br>      limit: 500<br>      dynamic_fields: [{category: table_calculation, expression: &#39;running_total(${user.count})&#39;,<br>          label: Total Users, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>          _kind_hint: measure, table_calculation: total_users, _type_hint: number,<br>          is_disabled: true}]<br>      join_fields: []<br>    - model: system__activity<br>      explore: history<br>      type: table<br>      fields: [history.dashboard_run_count, history.average_runtime, history.completed_week]<br>      fill_fields: [history.completed_week]<br>      filters:<br>        history.completed_month: 3 months<br>      limit: 500<br>      join_fields:<br>      - field_name: history.completed_week<br>        source_field_name: user.created_week<br>    color_application:<br>      collection_id: bergfreunde<br>      palette_id: bergfreunde-categorical-0<br>      options:<br>        steps: 5<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    y_axes: [{label: &#39;&#39;, orientation: left, series: [{axisId: user.count, id: user.count,<br>            name: Users Added}, {axisId: history.dashboard_run_count, id: history.dashboard_run_count,<br>            name: Dashboard Run Count}], showLabels: true, showValues: true, unpinAxis: false,<br>        tickDensity: default, type: linear}, {label: !!null &#39;&#39;, orientation: right,<br>        series: [{axisId: average_runtime_seconds, id: average_runtime_seconds, name: &#39;Average<br>              Runtime Seconds &#39;}, {axisId: history.average_runtime, id: history.average_runtime,<br>            name: Average Runtime in Seconds}], showLabels: true, showValues: true,<br>        unpinAxis: false, tickDensity: default, type: linear}]<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    series_types:<br>      user.count: scatter<br>    point_style: none<br>    series_colors:<br>      total_users: &quot;#222&quot;<br>      history.dashboard_run_count: &quot;#2C72AC&quot;<br>    series_labels:<br>      user.count: Users Added<br>    series_point_styles:<br>      user.count: triangle<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: false<br>    interpolation: linear<br>    type: looker_line<br>    hidden_fields: [history.average_runtime]<br>    sorts: [user.created_week desc]<br>    column_limit: 50<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${history.average_runtime}&quot;,<br>        label: &#39;Average Runtime Seconds &#39;, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: average_runtime_seconds, _type_hint: number}]<br>    row: 6<br>    col: 0<br>    width: 24<br>    height: 8<br>  - title: DashBoard Count<br>    name: DashBoard Count<br>    model: system__activity<br>    explore: dashboard<br>    type: single_value<br>    fields: [dashboard.count, dashboard.count_last_30_days]<br>    filters:<br>      dashboard.moved_to_trash: &#39;No&#39;<br>    limit: 500<br>    column_limit: 50<br>    dynamic_fields: [{table_calculation: total_dashboards, label: Total Dashboards,<br>        expression: &#39;sum(${dashboard.count})&#39;, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: measure, _type_hint: number, is_disabled: true}, {table_calculation: last_30_days,<br>        label: Last 30 days, expression: &quot;sum(\n  if(diff_days(${dashboard.created_date},\<br>          \ now()) &lt;= 30, ${dashboard.count},0))&quot;, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: measure, _type_hint: number, is_disabled: true}, {measure: in_last_30_days,<br>        based_on: dashboard.id, type: count_distinct, label: In Last 30 Days, value_format: !!null &#39;&#39;,<br>        value_format_name: !!null &#39;&#39;, _kind_hint: measure, _type_hint: number, filter_expression: &#39;diff_days(${dashboard.created_date},<br>          now()) &lt;= 30&#39;}]<br>    custom_color_enabled: false<br>    show_single_value_title: true<br>    show_comparison: false<br>    comparison_type: change<br>    comparison_reverse_colors: false<br>    show_comparison_label: true<br>    enable_conditional_formatting: false<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    custom_color: forestgreen<br>    single_value_title: Dashboard Count<br>    comparison_label: Last 30 Days<br>    series_types: {}<br>    hidden_fields: []<br>    note_state: collapsed<br>    note_display: hover<br>    note_text: Total Non-Deleted Dashboards<br>    defaults_version: 1<br>    y_axes: []<br>    listen: {}<br>    row: 2<br>    col: 5<br>    width: 5<br>    height: 4<br>  - title: Unengaged Users<br>    name: Unengaged Users<br>    model: system__activity<br>    explore: user<br>    type: looker_grid<br>    fields: [user.id, user.name, user.created_date, user_facts.last_ui_login_date,<br>      history.most_recent_query_date, scheduled_plan.count, user_facts.last_ui_login_credential_type]<br>    filters:<br>      user_facts.last_ui_login_date: before 90 days ago<br>      user.is_disabled: &#39;No&#39;<br>      user_facts.is_looker_employee: &#39;No&#39;<br>    sorts: [user_facts.last_ui_login_date]<br>    limit: 100<br>    column_limit: 50<br>    dynamic_fields: [{table_calculation: no_query_login, label: &#39;No-Query Login?&#39;,<br>        expression: &quot;${history.most_recent_query_date} &lt; ${user_facts.last_ui_login_date}&quot;,<br>        value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        _type_hint: yesno}, {table_calculation: days_since_last_login, label: Days<br>          Since Last Login, expression: &#39;diff_days(${user_facts.last_ui_login_date},<br>          trunc_days(now()))&#39;, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: dimension, _type_hint: number}]<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d<br>      palette_id: c36094e3-d04d-4aa4-8ec7-bc9af9f851f4<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      user_facts.last_ui_login_date: Last Login<br>      user_facts.last_api_login_date: Last API Login Date<br>      user.name: Name<br>      user.created_date: Created Date<br>      history.most_recent_query_date: Last Query<br>      scheduled_plan.count: Count of Scheduled Plans<br>    series_cell_visualizations:<br>      days_since_last_login:<br>        is_active: true<br>        palette:<br>          palette_id: 2da48dd9-f8f5-45cc-81a6-74037767d59b<br>          collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d<br>    conditional_formatting: [{type: along a scale..., value: !!null &#39;&#39;, background_color: &quot;#81BE56&quot;,<br>        font_color: !!null &#39;&#39;, color_application: {collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d,<br>          palette_id: e26878fa-802e-47d9-9478-62fb4307f763, options: {steps: 32, constraints: {<br>              min: {type: number, value: 10}, mid: {type: middle}, max: {type: number,<br>                value: 200}}, reverse: true, stepped: false}}, bold: false, italic: false,<br>        strikethrough: false, fields: [days_since_last_login]}]<br>    truncate_column_names: false<br>    hidden_fields: [user.id, no_query_login, user_facts.last_ui_login_date, user_facts.last_ui_login_credential_type,<br>      user.created_date, scheduled_plan.count, history.most_recent_query_date]<br>    note_state: collapsed<br>    note_display: hover<br>    note_text: Users who have not authenticated into Looker in the last 90 days.<br>    defaults_version: 1<br>    series_types: {}<br>    y_axes: []<br>    listen: {}<br>    row: 40<br>    col: 12<br>    width: 12<br>    height: 8<br>  - title: Queue Time for Execution<br>    name: Queue Time for Execution<br>    model: system__activity<br>    explore: scheduled_plan<br>    type: looker_grid<br>    fields: [scheduled_job_stage.avg_runtime, scheduled_job.count, dashboard.title]<br>    filters:<br>      scheduled_job_stage.stage: &#39;&quot;enqueue_for_execute&quot;&#39;<br>      scheduled_job.created_date: 30 days ago for 30 days<br>    sorts: [scheduled_job_stage.avg_runtime desc]<br>    limit: 500<br>    column_limit: 50<br>    show_view_names: false<br>    show_row_numbers: false<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: transparent<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: true<br>    color_application:<br>      collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d<br>      palette_id: c36094e3-d04d-4aa4-8ec7-bc9af9f851f4<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    truncate_header: false<br>    series_labels:<br>      scheduled_job_stage.avg_runtime: Average Time in Queue<br>      scheduled_job.count: Run Count<br>    series_cell_visualizations:<br>      scheduled_job_stage.avg_runtime:<br>        is_active: false<br>        palette:<br>          palette_id: e26878fa-802e-47d9-9478-62fb4307f763<br>          collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d<br>    conditional_formatting: [{type: along a scale..., value: !!null &#39;&#39;, background_color: &quot;#81BE56&quot;,<br>        font_color: !!null &#39;&#39;, color_application: {collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d,<br>          palette_id: e26878fa-802e-47d9-9478-62fb4307f763, options: {steps: 5, constraints: {<br>              min: {type: minimum}, mid: {type: middle}, max: {type: maximum}}, mirror: true,<br>            reverse: true, stepped: false}}, bold: false, italic: false, strikethrough: false,<br>        fields: [scheduled_job_stage.avg_runtime]}, {type: along a scale..., value: !!null &#39;&#39;,<br>        background_color: &quot;#81BE56&quot;, font_color: !!null &#39;&#39;, color_application: {collection_id: aed851c8-b22d-4b01-8fff-4b02b91fe78d,<br>          custom: {id: 3824bfef-80a2-2fb2-cb03-c0e767fc1658, label: Custom, type: continuous,<br>            stops: [{color: &quot;#FFFFFF&quot;, offset: 0}, {color: &quot;#fa461f&quot;, offset: 100}]},<br>          options: {steps: 5, constraints: {min: {type: minimum}, mid: {type: middle},<br>              max: {type: maximum}}, mirror: true, reverse: false, stepped: false}},<br>        bold: false, italic: false, strikethrough: false, fields: [scheduled_job.count]}]<br>    truncate_column_names: false<br>    series_types: {}<br>    defaults_version: 1<br>    hidden_fields: []<br>    y_axes: []<br>    listen: {}<br>    row: 32<br>    col: 0<br>    width: 12<br>    height: 8<br>  - title: Query Over 300 Seconds L30D<br>    name: Query Over 300 Seconds L30D<br>    model: system__activity<br>    explore: history<br>    type: looker_grid<br>    fields: [history.issuer_source, history.real_dash_id, history.connection_name,<br>      history.cache, dashboard.title, history.completed_date, history.runtime, history.id]<br>    filters:<br>      history.completed_date: 30 days<br>      history.runtime_tiers: 300 or Above<br>      history.issuer_source: &quot;-API,-Action Hub,-Other&quot;<br>    sorts: [history.completed_date desc]<br>    limit: 500<br>    query_timezone: America/Denver<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: normal<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: true<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: bergfreunde_2<br>      palette_id: bergfreunde_2-categorical-0<br>      options:<br>        steps: 5<br>    font_size: &#39;12&#39;<br>    series_types: {}<br>    series_colors: {}<br>    charts_across: 4<br>    defaults_version: 1<br>    value_labels: legend<br>    label_type: labPer<br>    hidden_series: []<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, history.id, dashboard.title, history.real_dash_id,<br>      history.completed_date, history.issuer_source, history.connection_name, history.cache,<br>      history.runtime]<br>    series_column_widths:<br>      dashboard.title: 195<br>      history.real_dash_id: 167<br>      history.completed_date: 122<br>      history.issuer_source: 110<br>      history.connection_name: 217<br>      history.cache: 187<br>      history.runtime: 143<br>      history.id: 107<br>    hidden_fields: []<br>    y_axes: []<br>    listen: {}<br>    row: 48<br>    col: 0<br>    width: 24<br>    height: 6<br>  - title: PDT Builds L30D<br>    name: PDT Builds L30D<br>    model: system__activity<br>    explore: pdt_builds<br>    type: looker_grid<br>    fields: [pdt_builds.build_reason, pdt_builds.average_build_time_seconds, pdt_builds.average_build_time_minutes]<br>    fill_fields: [pdt_builds.build_reason]<br>    filters:<br>      pdt_builds.end_date: 30 days<br>    sorts: [pdt_builds.average_build_time_seconds desc]<br>    limit: 500<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${pdt_builds.average_build_time_seconds}&quot;,<br>        label: AVG Build Time Seconds, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: avg_build_time_seconds, _type_hint: number}]<br>    query_timezone: America/Denver<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_cell_visualizations:<br>      pdt_builds.average_build_time_seconds:<br>        is_active: true<br>      avg_build_time_seconds:<br>        is_active: true<br>        palette:<br>          palette_id: 471a8295-662d-46fc-bd2d-2d0acd370c1e<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    series_types: {}<br>    hidden_fields: [pdt_builds.average_build_time_seconds, pdt_builds.average_build_time_minutes]<br>    y_axes: []<br>    listen: {}<br>    row: 64<br>    col: 0<br>    width: 12<br>    height: 5<br>  - title: PDT Builds by Result L30D<br>    name: PDT Builds by Result L30D<br>    model: system__activity<br>    explore: pdt_builds<br>    type: looker_grid<br>    fields: [pdt_builds.build_result, count_of_end_time, build_result, sum_of_elapsed_seconds]<br>    filters:<br>      pdt_builds.end_date: 30 days<br>      count_of_end_time: NOT NULL<br>    sorts: [run_count desc]<br>    limit: 500<br>    dynamic_fields: [{measure: count_of_end_time, based_on: pdt_builds.end_time, expression: &#39;&#39;,<br>        label: Count of End Time, type: count_distinct, _kind_hint: measure, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_end_time}&quot;, label: Run<br>          Count, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        table_calculation: run_count, _type_hint: number}, {category: dimension, expression: &#39;if(${pdt_builds.build_result}<br>          = &quot;Successful Build&quot;, &quot;Success&quot;,&quot;Failure&quot;)&#39;, label: Build Result, value_format: !!null &#39;&#39;,<br>        value_format_name: !!null &#39;&#39;, dimension: build_result, _kind_hint: dimension,<br>        _type_hint: string}, {measure: count_of_elapsed_seconds, based_on: pdt_builds.elapsed_seconds,<br>        expression: &#39;&#39;, label: Count of Elapsed Seconds, type: count_distinct, _kind_hint: measure,<br>        _type_hint: number}, {measure: sum_of_elapsed_seconds, based_on: pdt_builds.elapsed_seconds,<br>        expression: &#39;&#39;, label: Sum of Elapsed Seconds, type: sum, _kind_hint: measure,<br>        _type_hint: number}, {measure: sum_of_elapsed_minutes, based_on: pdt_builds.elapsed_minutes,<br>        expression: &#39;&#39;, label: Sum of Elapsed Minutes, type: sum, _kind_hint: measure,<br>        _type_hint: number}]<br>    query_timezone: America/Denver<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: 7c79334a-9912-4ca1-be6a-35756782ae09<br>      palette_id: de0bdb92-9455-489c-afa7-f0e0fdc76078<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, pdt_builds.view_name, pdt_builds.build_result,<br>      pdt_builds.start_date]<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      count_of_elapsed_seconds: Run Seconds<br>      sum_of_elapsed_seconds: Run Seconds<br>      sum_of_elapsed_minutes: Run Minutes<br>    series_column_widths:<br>      pdt_builds.view_name: 311<br>    series_cell_visualizations:<br>      count_of_end_time:<br>        is_active: false<br>        palette:<br>          palette_id: 1e4d66b9-f066-4c33-b0b7-cc10b4810688<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>      run_count:<br>        is_active: false<br>        palette:<br>          palette_id: 9bba0279-71a4-410a-bd57-3afc0dfabaad<br>          collection_id: 7c79334a-9912-4ca1-be6a-35756782ae09<br>    series_text_format:<br>      run_count: {}<br>      count_of_elapsed_seconds:<br>        align: left<br>      sum_of_elapsed_seconds:<br>        align: left<br>    conditional_formatting: []<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: normal<br>    legend_position: center<br>    series_types: {}<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    hidden_fields: [count_of_end_time, build_result]<br>    y_axes: []<br>    listen: {}<br>    row: 64<br>    col: 12<br>    width: 12<br>    height: 5<br>  - title: PDT Build Success vs Failure 30D<br>    name: PDT Build Success vs Failure 30D<br>    model: system__activity<br>    explore: pdt_builds<br>    type: looker_area<br>    fields: [count_of_end_time, build_results, pdt_builds.end_date]<br>    pivots: [build_results]<br>    fill_fields: [pdt_builds.end_date]<br>    filters:<br>      pdt_builds.end_month: 30 days<br>    sorts: [build_results, pdt_builds.end_date desc]<br>    limit: 500<br>    dynamic_fields: [{measure: count_of_end_time, based_on: pdt_builds.end_time, expression: &#39;&#39;,<br>        label: Count of End Time, type: count_distinct, _kind_hint: measure, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_end_time}&quot;, label: Run<br>          Count, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        table_calculation: run_count, _type_hint: number}, {category: dimension, expression: &#39;if(${pdt_builds.build_result}<br>          = &quot;Successful Build&quot;, &quot;Success&quot;,&quot;Failure&quot;)&#39;, label: Build Results, value_format: !!null &#39;&#39;,<br>        value_format_name: !!null &#39;&#39;, dimension: build_results, _kind_hint: measure,<br>        _type_hint: string}]<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    show_null_points: true<br>    interpolation: linear<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    color_application:<br>      collection_id: 7c79334a-9912-4ca1-be6a-35756782ae09<br>      palette_id: de0bdb92-9455-489c-afa7-f0e0fdc76078<br>    y_axes: []<br>    x_axis_zoom: true<br>    y_axis_zoom: true<br>    series_types: {}<br>    series_colors:<br>      Success - run_count: &quot;#068993&quot;<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, pdt_builds.view_name, pdt_builds.build_result,<br>      pdt_builds.start_date]<br>    show_totals: true<br>    show_row_totals: true<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    size_to_fit: true<br>    series_column_widths:<br>      pdt_builds.view_name: 311<br>    series_cell_visualizations:<br>      count_of_end_time:<br>        is_active: false<br>        palette:<br>          palette_id: 1e4d66b9-f066-4c33-b0b7-cc10b4810688<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    table_theme: white<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting: [{type: along a scale..., value: !!null &#39;&#39;, background_color: &quot;#F15922&quot;,<br>        font_color: !!null &#39;&#39;, color_application: {collection_id: 7c79334a-9912-4ca1-be6a-35756782ae09,<br>          palette_id: 5b289dc9-1446-49e6-ab05-ba239a94b7a9, options: {steps: 5, reverse: false}},<br>        bold: false, italic: false, strikethrough: false, fields: !!null &#39;&#39;}]<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    ordering: none<br>    show_null_labels: false<br>    defaults_version: 1<br>    hide_totals: false<br>    hide_row_totals: false<br>    hidden_fields: [count_of_end_time]<br>    listen: {}<br>    row: 56<br>    col: 0<br>    width: 24<br>    height: 8<br>  - name: PDT Build Monitoring<br>    type: text<br>    title_text: PDT Build Monitoring<br>    body_text: &#39;&#39;<br>    row: 54<br>    col: 0<br>    width: 24<br>    height: 2<br>  - title: PDT Runs by View L30D<br>    name: PDT Runs by View L30D<br>    model: system__activity<br>    explore: pdt_builds<br>    type: looker_column<br>    fields: [pdt_builds.view_name, count_of_end_time, build_results]<br>    pivots: [build_results]<br>    filters:<br>      pdt_builds.end_date: 30 days ago for 30 days<br>    sorts: [build_results, failure desc]<br>    limit: 500<br>    dynamic_fields: [{measure: count_of_end_time, based_on: pdt_builds.end_time, expression: &#39;&#39;,<br>        label: Count of End Time, type: count_distinct, _kind_hint: measure, _type_hint: number},<br>      {category: dimension, expression: &#39;if(${pdt_builds.build_result} = &quot;Successful<br>          Build&quot;, &quot;Success&quot;,&quot;Failure&quot;)&#39;, label: Build Results, value_format: !!null &#39;&#39;,<br>        value_format_name: !!null &#39;&#39;, dimension: build_results, _kind_hint: measure,<br>        _type_hint: string}, {category: table_calculation, expression: &quot;coalesce(pivot_where(${build_results}!=\&quot;\<br>          Success\&quot;, ${count_of_end_time}),0)\n/\ncoalesce(pivot_where(${build_results}=\&quot;\<br>          Success\&quot;, ${count_of_end_time}),0)&quot;, label: &quot;%&quot;, value_format: !!null &#39;&#39;,<br>        value_format_name: percent_0, _kind_hint: supermeasure, table_calculation: calculation,<br>        _type_hint: number, is_disabled: true}, {category: table_calculation, expression: &#39;coalesce(${count_of_end_time},0)&#39;,<br>        label: Run Count, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        table_calculation: run_count, _type_hint: number}, {category: table_calculation,<br>        expression: &quot;(pivot_index(${run_count},1))\n/\n(pivot_index(${run_count},1)\n\<br>          +\npivot_index(${run_count},2)\n)&quot;, label: &quot;% Failure&quot;, value_format: !!null &#39;&#39;,<br>        value_format_name: percent_0, _kind_hint: supermeasure, table_calculation: failure,<br>        _type_hint: number}]<br>    query_timezone: America/Denver<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_view_names: false<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: percent<br>    limit_displayed_rows: false<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    series_types: {}<br>    series_colors:<br>      Failure - count_of_end_time: &quot;#B32F37&quot;<br>      Success - count_of_end_time: &quot;#72D16D&quot;<br>      Failure - run_count: &quot;#B32F37&quot;<br>      Success - run_count: &quot;#72D16D&quot;<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: 12<br>    rows_font_size: 12<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    defaults_version: 1<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, pdt_builds.view_name, pdt_builds.build_result,<br>      pdt_builds.start_date]<br>    series_column_widths:<br>      pdt_builds.view_name: 311<br>    hidden_fields: [count_of_end_time, new_calculation, failure]<br>    y_axes: []<br>    listen: {}<br>    row: 77<br>    col: 0<br>    width: 24<br>    height: 10<br>  - title: Current Failing Views L30D<br>    name: Current Failing Views L30D<br>    model: system__activity<br>    explore: pdt_event_log<br>    type: looker_grid<br>    fields: [pdt_builds.view_name, count_of_end_time, build_results, sum_of_elapsed_seconds_2]<br>    pivots: [build_results]<br>    filters:<br>      pdt_builds.end_date: 30 days<br>      build_results: Failure<br>    sorts: [build_results, sum_of_elapsed_seconds_2 desc 0]<br>    limit: 5000<br>    column_limit: 50<br>    total: true<br>    dynamic_fields: [{measure: sum_of_elapsed_seconds, based_on: pdt_builds.elapsed_seconds,<br>        expression: &#39;&#39;, label: Sum of Elapsed Seconds, type: sum, _kind_hint: measure,<br>        _type_hint: number}, {measure: count_of_action_data, based_on: pdt_event_log.action_data,<br>        expression: &#39;&#39;, label: Count of Action Data, type: count_distinct, _kind_hint: measure,<br>        _type_hint: number}, {measure: count_of_end_time, based_on: pdt_builds.end_time,<br>        expression: &#39;&#39;, label: Count of End Time, type: count_distinct, _kind_hint: measure,<br>        _type_hint: number}, {category: dimension, expression: &#39;if(${pdt_builds.build_result}<br>          = &quot;Successful Build&quot;, &quot;Success&quot;,&quot;Failure&quot;)&#39;, label: Build Results, value_format: !!null &#39;&#39;,<br>        value_format_name: !!null &#39;&#39;, dimension: build_results, _kind_hint: measure,<br>        _type_hint: string}, {category: table_calculation, expression: &#39;pivot_index(${build_results},1)&#39;,<br>        label: Successful Builds, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: supermeasure, table_calculation: successful_builds, _type_hint: string,<br>        is_disabled: true}, {category: table_calculation, expression: &#39;pivot_index(${build_results},<br>          1)&#39;, label: New Calculation, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: supermeasure, table_calculation: new_calculation, _type_hint: string,<br>        is_disabled: true}, {measure: sum_of_elapsed_seconds_2, based_on: pdt_builds.elapsed_seconds,<br>        expression: &#39;&#39;, label: Sum of Elapsed Seconds, type: sum, _kind_hint: measure,<br>        _type_hint: number}, {measure: sum_of_elapsed_minutes, based_on: pdt_builds.elapsed_minutes,<br>        expression: &#39;&#39;, label: Sum of Elapsed Minutes, type: sum, _kind_hint: measure,<br>        _type_hint: number}]<br>    query_timezone: America/Denver<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    pinned_columns:<br>      &quot;$$$_row_numbers_$$$&quot;: left<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, pdt_builds.view_name, pdt_event_log.action_data]<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      count_of_end_time: Run Count<br>      sum_of_elapsed_seconds_2: Seconds Wasted<br>    series_column_widths:<br>      pdt_event_log.action_data: 2873<br>      pdt_builds.build_result: 133<br>      pdt_builds.elapsed_seconds: 128<br>      pdt_builds.end_time: 148<br>      pdt_event_log.view_name: 188<br>      pdt_event_log.action: 154<br>      pdt_event_log.created_time: 147<br>      pdt_builds.build_reason: 187<br>      pdt_builds.view_name: 406<br>      sum_of_elapsed_seconds: 169<br>    series_cell_visualizations:<br>      count_of_end_time:<br>        is_active: false<br>        palette:<br>          palette_id: 2d9abb49-d953-c441-86f3-46e444d69836<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>          custom_colors:<br>          - &quot;#3be617&quot;<br>          - &quot;#6afa55&quot;<br>          - &quot;#f6ff7c&quot;<br>          - &quot;#f27748&quot;<br>          - &quot;#ff8352&quot;<br>      sum_of_elapsed_seconds_2:<br>        is_active: true<br>        palette:<br>          palette_id: &#39;09bb30be-bc4f-18bf-133c-bf4d6f756d80&#39;<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>          custom_colors:<br>          - &quot;#f7fa59&quot;<br>          - &quot;#feb647&quot;<br>          - &quot;#f5924c&quot;<br>          - &quot;#ff6d45&quot;<br>          - &quot;#f24b2e&quot;<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    series_types: {}<br>    series_text_format:<br>      count_of_end_time:<br>        align: left<br>    hidden_fields: []<br>    y_axes: []<br>    listen: {}<br>    row: 69<br>    col: 0<br>    width: 24<br>    height: 8<br>  - name: Other<br>    type: text<br>    title_text: Other<br>    body_text: &#39;&#39;<br>    row: 130<br>    col: 0<br>    width: 24<br>    height: 2<br>  - name: Completed Queries by Explore L30D<br>    title: Completed Queries by Explore L30D<br>    merged_queries:<br>    - model: system__activity<br>      explore: history<br>      type: table<br>      fields: [query.view]<br>      limit: 500<br>      join_fields: []<br>    - model: system__activity<br>      explore: history<br>      type: table<br>      fields: [query.view, history.query_run_count]<br>      filters:<br>        history.completed_month: 30 days ago for 30 days<br>      sorts: [history.query_run_count desc]<br>      limit: 500<br>      join_fields:<br>      - field_name: query.view<br>        source_field_name: query.view<br>    type: looker_column<br>    sorts: [history.query_run_count desc]<br>    column_limit: 50<br>    row: 23<br>    col: 0<br>    width: 24<br>    height: 9<br>  - title: Scheduled Plan Count (Looks)<br>    name: Scheduled Plan Count (Looks)<br>    model: system__activity<br>    explore: scheduled_plan<br>    type: looker_grid<br>    fields: [count_of_id_2, count_of_user_id, count_of_address, look.title]<br>    filters:<br>      look.title: &quot;-NULL&quot;<br>    sorts: [count_of_id_2 desc]<br>    limit: 500<br>    column_limit: 50<br>    dynamic_fields: [{category: table_calculation, expression: &quot;${count_of_id_2}&quot;,<br>        label: Schedule Count, value_format: !!null &#39;&#39;, value_format_name: decimal_0,<br>        _kind_hint: measure, table_calculation: schedule_count, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_user_id}&quot;, label: Count<br>          of Users (Scheduler), value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;,<br>        _kind_hint: measure, table_calculation: count_of_users_scheduler, _type_hint: number},<br>      {category: table_calculation, expression: &quot;${count_of_address}&quot;, label: Recipient<br>          Count, value_format: !!null &#39;&#39;, value_format_name: !!null &#39;&#39;, _kind_hint: measure,<br>        table_calculation: recipient_count, _type_hint: number}, {measure: count_of_id,<br>        based_on: scheduled_job.id, expression: &#39;&#39;, label: Count of ID, type: count_distinct,<br>        _kind_hint: measure, _type_hint: number}, {category: measure, expression: &#39;&#39;,<br>        label: Count of User ID, based_on: scheduled_plan.user_id, _kind_hint: measure,<br>        measure: count_of_user_id, type: count_distinct, _type_hint: number}, {measure: count_of_address,<br>        based_on: scheduled_plan_destination.address, expression: &#39;&#39;, label: Count<br>          of Address, type: count_distinct, _kind_hint: measure, _type_hint: number},<br>      {measure: count_of_id_2, based_on: scheduled_plan.id, expression: &#39;&#39;, label: Count<br>          of ID, type: count_distinct, _kind_hint: measure, _type_hint: number}]<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: true<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: false<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    show_sql_query_menu_options: false<br>    column_order: [&quot;$$$_row_numbers_$$$&quot;, look.title, schedule_count, count_of_users_scheduler,<br>      recipient_count]<br>    show_totals: true<br>    show_row_totals: true<br>    series_cell_visualizations:<br>      count_of_id:<br>        is_active: false<br>        palette:<br>          palette_id: 1e4d66b9-f066-4c33-b0b7-cc10b4810688<br>          collection_id: b43731d5-dc87-4a8e-b807-635bef3948e7<br>    series_text_format:<br>      recipient_count:<br>        align: left<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    series_types: {}<br>    hidden_fields: [count_of_user_id, count_of_address, count_of_id_2]<br>    y_axes: []<br>    listen: {}<br>    row: 124<br>    col: 0<br>    width: 24<br>    height: 6<br>  - title: Dashboard Recommendations<br>    name: Dashboard Recommendations<br>    model: system__activity<br>    explore: dashboard<br>    type: looker_grid<br>    fields: [dashboard_element.high_merge_query_count, dashboard_element.high_query_count,<br>      dashboard_element.low_auto_refresh_interval, dashboard_element.sorted_warnings,<br>      user.name, dashboard_element.combo_warning, dashboard.title, dashboard_element.combo_recommendation]<br>    filters:<br>      dashboard.moved_to_trash: &#39;No&#39;<br>      dashboard_element.sorted_warnings: &quot;&gt;0&quot;<br>    sorts: [dashboard_element.sorted_warnings desc]<br>    limit: 100<br>    column_limit: 50<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: false<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: 5591d8d1-6b49-4f8e-bafa-b874d82f8eb7<br>      palette_id: 18d0c733-1d87-42a9-934f-4ba8ef81d736<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      dashboard_element.sorted_warnings: Severity<br>      dashboard_element.combo_warning: Warnings<br>      dashboard_element.combo_recommendation: Recommendations<br>    series_column_widths:<br>      dashboard.id: 166<br>      dashboard.title: 225<br>      dashboard_element.sorted_warnings: 65<br>    series_cell_visualizations:<br>      dashboard_element.sorted_warnings:<br>        is_active: false<br>    series_text_format:<br>      dashboard_element.sorted_warnings: {}<br>      dashboard_element.combo_warning:<br>        align: left<br>      dashboard_element.combo_recommendation:<br>        align: left<br>    conditional_formatting: [{type: along a scale..., value: !!null &#39;&#39;, background_color: &quot;#3D52B9&quot;,<br>        font_color: !!null &#39;&#39;, color_application: {collection_id: 5591d8d1-6b49-4f8e-bafa-b874d82f8eb7,<br>          palette_id: 5378478f-6725-4b04-89cc-75fc42da804e, options: {steps: 5, constraints: {<br>              max: {type: number, value: 15}}}}, bold: false, italic: false, strikethrough: false,<br>        fields: [dashboard_element.sorted_warnings]}]<br>    hidden_fields: [user.name, dashboard_element.high_merge_query_count, dashboard_element.high_query_count,<br>      dashboard_element.low_auto_refresh_interval]<br>    defaults_version: 1<br>    listen: {}<br>    row: 139<br>    col: 0<br>    width: 24<br>    height: 8<br>  - title: Explore Recommendations<br>    name: Explore Recommendations<br>    model: system__activity<br>    explore: query_metrics<br>    type: looker_grid<br>    fields: [query.view, query.model, history.connection_name, query_metrics.async_processing_average,<br>      query_metrics.prepare_average, query_metrics.explore_init_average, query_metrics.marshalled_cache_load_average,<br>      query_metrics.model_init_computed_average, query_metrics.acquire_connection_average,<br>      query_metrics.execute_main_query_average, query_metrics.postprocessing_average,<br>      query_metrics.stream_to_cache_average, query_metrics.sorted_warnings, query_metrics.combo_warning,<br>      query_metrics.combo_recommendations]<br>    filters:<br>      query.view: &quot;-EMPTY&quot;<br>      query.model: &quot;-EMPTY&quot;<br>      query_metrics.minimum_query_events: &#39;30&#39;<br>      query_metrics.sorted_warnings: &quot;&gt;0&quot;<br>      query_metrics.combo_recommendations: &quot;-EMPTY&quot;<br>      query_metrics.combo_warning: &quot;%time%&quot;<br>    sorts: [query_metrics.sorted_warnings desc]<br>    limit: 500<br>    column_limit: 50<br>    show_view_names: false<br>    show_row_numbers: true<br>    transpose: false<br>    truncate_text: false<br>    hide_totals: false<br>    hide_row_totals: false<br>    size_to_fit: true<br>    table_theme: white<br>    limit_displayed_rows: false<br>    enable_conditional_formatting: true<br>    header_text_alignment: left<br>    header_font_size: &#39;12&#39;<br>    rows_font_size: &#39;12&#39;<br>    conditional_formatting_include_totals: false<br>    conditional_formatting_include_nulls: false<br>    color_application:<br>      collection_id: 5591d8d1-6b49-4f8e-bafa-b874d82f8eb7<br>      palette_id: 18d0c733-1d87-42a9-934f-4ba8ef81d736<br>    show_sql_query_menu_options: false<br>    show_totals: true<br>    show_row_totals: true<br>    series_labels:<br>      query_metrics.sorted_warnings: Severity<br>      query_metrics.combo_warning: Warnings<br>      query_metrics.combo_recommendations: Recommendations<br>    series_column_widths:<br>      query_metrics.stream_to_cache_average: 75<br>      query.view: 55<br>      query.model: 55<br>      history.connection_name: 55<br>      query_metrics.sorted_warnings: 55<br>    series_cell_visualizations:<br>      query_metrics.async_processing_average:<br>        is_active: true<br>    series_text_format:<br>      query_metrics.combo_warning:<br>        align: left<br>      query_metrics.combo_recommendations:<br>        align: left<br>    conditional_formatting: [{type: along a scale..., value: 0, background_color: &quot;#FC2E31&quot;,<br>        font_color: !!null &#39;&#39;, color_application: {collection_id: 5591d8d1-6b49-4f8e-bafa-b874d82f8eb7,<br>          palette_id: 5378478f-6725-4b04-89cc-75fc42da804e, options: {steps: 4, constraints: {<br>              min: {type: number, value: 0}, mid: {type: number, value: 1}, max: {<br>                type: number, value: 6}}, stepped: false}}, bold: false, italic: false,<br>        strikethrough: false, fields: !!null &#39;&#39;}]<br>    x_axis_gridlines: false<br>    y_axis_gridlines: true<br>    show_y_axis_labels: true<br>    show_y_axis_ticks: true<br>    y_axis_tick_density: default<br>    y_axis_tick_density_custom: 5<br>    show_x_axis_label: true<br>    show_x_axis_ticks: true<br>    y_axis_scale_mode: linear<br>    x_axis_reversed: false<br>    y_axis_reversed: false<br>    plot_size_by_field: false<br>    trellis: &#39;&#39;<br>    stacking: &#39;&#39;<br>    legend_position: center<br>    point_style: none<br>    show_value_labels: false<br>    label_density: 25<br>    x_axis_scale: auto<br>    y_axis_combined: true<br>    ordering: none<br>    show_null_labels: false<br>    show_totals_labels: false<br>    show_silhouette: false<br>    totals_color: &quot;#808080&quot;<br>    defaults_version: 1<br>    series_types: {}<br>    hidden_fields: [query_metrics.async_processing_average, query_metrics.prepare_average,<br>      query_metrics.explore_init_average, query_metrics.marshalled_cache_load_average,<br>      query_metrics.model_init_computed_average, query_metrics.acquire_connection_average,<br>      query_metrics.execute_main_query_average, query_metrics.postprocessing_average,<br>      query_metrics.stream_to_cache_average]<br>    listen: {}<br>    row: 147<br>    col: 0<br>    width: 24<br>    height: 9</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=759cc5fb232b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Lessons I Have Learned Using dbt]]></title>
            <link>https://eric-arsenaults.medium.com/5-lessons-i-learned-using-dbt-9fa3c70957a3?source=rss-b834b13dd535------2</link>
            <guid isPermaLink="false">https://medium.com/p/9fa3c70957a3</guid>
            <category><![CDATA[dbt]]></category>
            <category><![CDATA[data-pipeline]]></category>
            <category><![CDATA[airflow]]></category>
            <category><![CDATA[analytics-engineering]]></category>
            <category><![CDATA[data-engineering]]></category>
            <dc:creator><![CDATA[Eric Arsenault]]></dc:creator>
            <pubDate>Mon, 20 Mar 2023 19:31:10 GMT</pubDate>
            <atom:updated>2023-05-31T19:55:46.824Z</atom:updated>
            <content:encoded><![CDATA[<h3>5 Lessons I Have Learned Using <em>dbt Core</em></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Xmet6782MrMOYqOl.jpg" /></figure><p>Over the past few years I have managed quite a few dbt Core projects while working various consulting and data team jobs. While I really enjoy modeling data with dbt Core, it can be a serious headache when it’s implemented poorly. Here are 5 things that I have learned that can help build a great project:</p><h3>1. Follow the dbt Labs style guide</h3><p>The first thing that I recommend is to follow the <a href="https://github.com/dbt-labs/corp/blob/main/dbt_style_guide.md">style guide published by dbt Labs</a>. I think this style guide is great; it covers all aspects of a good project but is still pretty concise and easy to understand. Even if you don’t end up following the entire thing word for word, it’s a good starting point. I think it’s a good idea to give it a read over and see what rules you want to enforce in your project. Some of the areas of the style guide that I think are most important are:</p><ul><li>General project structure with stg and mart models</li><li>Importing all of the tables at the top of the file</li><li>Use CTE over window functions whenever possible</li><li>Prioritize readability in code instead of focusing on fewer lines</li><li>Table alias names instead of single letters (o.count -&gt; orders.count)</li></ul><p>With that said, these may not be the points that you find most important. Regardless of whether you use everything on the style guide exactly how it’s listed or change it a bit to navigate your own use case, I think that for the most part this is a great starting point for anyone writing models.</p><h3>2. Don’t overdue it with jinja or macros</h3><p>Don’t get me wrong, jinja and macros are both great. They are essential pieces of dbt Core that can be eternally helpful when used correctly. With that said they add an extra layer of complexity to the code that shouldn’t be used unless it’s necessary. One of the great strengths of dbt Core is that it allows for complex data modeling while still mostly just using pure SQL. Adding in more complexity and taking things farther away from pure SQL comes with some downsides. The first downside is that it will be more difficult for a new engineer to understand the code; SQL is universally understood amongst data folks, but jinja and macros will both may take some up-skilling to use. While it may not be a substantial up-skilling for some engineers, it is something to consider. The second and arguably more influential reason is that it will make it much harder to migrate off dbt Core if that time ever does comes. Someday if you do decide to migrate off of dbt Core it could be a simple copy-paste job to another SQL based platform, or you may need to refactor and rewrite all of your models because they contain languages and features that are only included in dbt Core. For these reasons, in the projects that I manage I usually do not implement complex jinja or macros unless they are necessary and the value provided outweighs the negatives.</p><h3>3. Only Self Manage With DevOps Support</h3><p>There are a ton of choices when it comes to managing dbt Core. It is just a simple CLI tool, so engineers around the world have thought up countless ways to run it. I have actually <a href="https://pivot-computing.medium.com/my-3-favorite-ways-to-manage-dbt-896090037eb4">written an entire article about my 3 favorite ways to manage dbt Core</a>. Many companies decide to self manage dbt Core for two reasons: cost reduction and reducing PHI risk. By far the most popular method for self managing dbt Core is by running it on one of the managed airflow platforms like Astronomer or Google Composer. This method is pretty complicated, and requires a lot of engineering that is usually outside the skill set of most analytics engineers. Although an analytics engineer should be able to write a dag that executes a dbt Core project, they may not be able to setup and manage the infrastructure that the code executes on, manage a pipeline and storage for metadata, manage the CI/CD pipeline and setup alerting and monitoring. To do this you will need support from a DevOps or Cloud Engineer. Even if your analytics engineers have the skill to manage all of this, in my opinion you want them focused on modeling data, not managing the infrastructure that it runs on.</p><h3>4. Don’t Build a Giant Spider Web</h3><p>What I mean by this is that there are a lot of ways to organize a project. You can follow the style guide and use stg and mart folders which I would recommend, or create something of your own design. However you decide to organize your project, just make sure you have a cohesive plan going into it. Whether it be two distinct layers like the dbt Labs style guide suggests or something else that works better for your use case, make sure you aren’t building a huge spider web of dependent models without any obvious explanation. It can be very difficult to support environments like this, especially for new engineers on the project. If the project is organized poorly then debugging will be difficult and time consuming, bringing in new developers will be challenging and loosing any key team members will be daunting. For the sake of this article I am not going to go into how exactly you should organize your project, just make sure you have a plan that future engineers will be able to understand when they look at it.</p><h3>5. Don’t Use dbt Core for Use Cases Outside of Analytics</h3><p>Need live streaming data? Doing a machine learning project? Working with OLTP systems? dbt Core is not what you need. After using dbt Core extensively and seeing it succeed in some scenarios and fail in others, I think that it should only be used for use cases within analytics. I do not think that dbt Core is a general purpose data engineering tool that can be used for many use cases as some people suggest. I have found that it is remarkably good for modeling data for analytics and dashboard-ing, but not very good for use cases outside of this. In general if you are doing a data project outside of analytics, there are probably better tools to use. You wouldn&#39;t use a hammer to hit a screw, would you? The same logic applies here; it is a great tool but make sure you are using the correct tool for the job.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9fa3c70957a3" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>