LogoLogo
  • Introduction
    • Overview
    • Why Alvin?
    • Connect your systems
      • Data Warehouse
        • BigQuery
          • Provision source system credentials
          • Provision with GCloud CLI
        • Snowflake
        • Databricks
      • Business Intelligence
        • Looker
      • Orchestration
        • dbt
      • SSO (Single Sign-On)
    • Security & compliance
    • Types of metadata
    • FAQ
  • Cost Monitoring
    • Introduction to Cost Monitoring
    • Compute
    • Storage
  • BI Query Optimizer
    • Introduction to Query Optimizer
    • How does it work?
    • Getting started
  • Workflow automation
    • Introduction to Workflow Automation
    • Events definitions
    • Configuring Workflows
  • Anomaly Detection
    • Anomaly Detection
  • Exploring Metadata
    • Lineage
      • Depth of lineage
    • Impact Analysis
    • Entities
    • Entity View
    • Metadata Warehouse
Powered by GitBook
On this page
  1. Cost Monitoring

Compute

Fine-tune your workloads to optimize costs and efficiency of your environment.

PreviousIntroduction to Cost MonitoringNextStorage

Last updated 5 months ago

Understand how your environment changes over time, what affects your overall spend and spot anomalies related to your Warehouse, orchestration and analytical usage.

Workloads allows you to segment queries running within your data warehouse into distinct groups and zoom into each group's metrics with a specialized lens.

They are grouped by analytical queries from your connected BI environment, dbt models materializing over time, users and service accounts, GCP projects and more. We also separate Query Fingerprints – it’s queries without the literals (stream, numbers, parameters) or limits, to get to the base structure of queries and changes that happen to those patterns over time. It allows you to understand what drives your Warehouse costs at an aggregated level.

Even further, you are able to add your own custom apps, workloads, owners, teams and domains simply by adding tags/labels or query comments, which will then be picked up by Alvin. This can be seen in the screenshot under from our own environment, where all the product features are labelled and thereby creating their own workloads.