The Spotlight features are currently in beta.We’re actively testing and improving them — some of the functionality might be subject to change.

​
Getting Started

Lightdash users don’t need to do anything to get started! Spotlight features use your existing Lightdash semantic layer and metrics definitions, so you can get started today. Head to the Metrics Catalog under the Browse menu in the navigation bar.

​
Browsing the catalog

Browse all the project metrics you have access to (based on permissions and user-attributes) in the Metrics Catalog.
  1. Search: Easily find metrics by their names or .yml descriptions using the searchbar.
  2. View .yml descriptions: Click on any description to expand and view the full content, including rendered Markdown.
  3. Categories: Use categories to streamline your metrics and KPIs. Filter metrics by category and add new ones directly in the UI. Users with editor permissions and above can click on any category cell to edit, rename, change its color, or delete it.
  4. View popularity: Discover a metric’s popularity and see where it’s being used. Click to explore a complete list of charts which use the metric. Metrics are sorted by default to highlight the most used ones first.
  5. Explore: Interactive viewers and above can dive deeper by clicking Explore to visualize the metric in a chart format.

​
Exploring a metric

Visualize your metrics in the Metrics Explorer.
  1. Plot over time: View your selected metric plotted over a time dimension as a line chart. You can adjust this dimension or set a default time dimension in your .yml to simplify the process for users. See how
  2. Filter by date: Use the date picker with convenient presets for quick selection. See how default presets work based on the granularity
  3. Adjust the time granularity: Refine your view by choosing the desired level of date granularity.
  4. Filter by a dimension: Filter your metric by any string or boolean dimension from the same table.
  5. Segment-by: Break down the metric by any non-time dimension in your dataset.
  6. Compare to:
    • ‘This time last year’: Compare the selected time period to the same period last year
    • ‘Another metric’: Compare to any other metric in the project that has a default time dimension specified in the .yml. This includes joins See how
  7. Drag to zoom: Click and drag across the chart to highlight the desired time range or data points, then release to zoom in on that segment. Hit ‘Reset Zoom’ to reset chart.

​
Curating Spotlight for your business users

Spotlight is designed to be a tool for your business users to explore and understand your data. To make Spotlight more useful for your business users, you can curate the metrics they can see and explore. To do this, you can:
  • Control the visibility of metrics in the catalog
  • Add categories to your metrics
  • Add default time settings to your metrics
All through your Lightdash .yml files.

​
Configuring global visibility of metrics

You can control the visibility of metrics in the catalog by creating a new file called lightdash.config.yml in the root of your dbt project.
If you’re new to lightdash.config.yml, check out our getting started guide to learn how to create and set up this file.
See this video for an example on how to set this up:
Step-by-step guide
  1. Add the following to your lightdash.config.yml file:
spotlight:
  default_visibility: show
The default visibility can be set to show or hide.If you don’t set this, the default visibility will be show, so all metrics will be visible in the catalog by default (but other settings like user attributes will still apply).
This will set the default visibility of metrics in the catalog to show for all metrics in your project. You can also set this to hide if you prefer to hide metrics by default and then override this on a per-model/metric basis.
  1. Now that you’ve set the default visibility, you can override this on a per-model/metric basis.
models:
  - name: events
    meta:
      spotlight:
        visibility: hide
This will hide the events model from the catalog.
  1. If there are metrics in the events model that you want to make visible, you can override the default visibility for those metrics.
models:
  - name: events
    meta:
      spotlight:
        visibility: hide
    metrics:
      - name: event_count
        type: count
        spotlight:
          visibility: show
  1. Once you compile your project, you’ll see the event_count metric in the catalog, even though the events model is hidden.

​
Assigning categories to metrics

Categories are a great way to organize your metrics in the catalog. You can create a new category by adding a new categories field to your lightdash.config.yml file. Here’s a video showing how to set this up:
Step-by-step guide
  1. Add the following to your lightdash.config.yml file:
spotlight:
  categories:
    revenue: # Required, this is the name of the category, and how it will be referenced in the catalog. It must be unique.
      label: Revenue # Required, this is what will be displayed in the catalog
      color: "orange" # Optional, defaults to "gray", with the option to choose from a range of colors: "gray", "violet", "red", "orange", "green", "blue", "indigo", "pink", "yellow"
  1. Now that you’ve added a category, you can assign metrics to it by adding a categories field to your models .yml file.
models:
  - name: events
    meta:
      spotlight:
        visibility: show
        categories:
          - revenue
This will add the revenue category to all metrics in the events model. If you want to add another category to a specific metric, you can do so by adding the categories field to the metric’s .yml file. And remember, you can only add categories that have been defined in the lightdash.config.yml file.
  1. Now you can add the marketing category to the event_count metric: So in your lightdash.config.yml file, you need to have another category. Let’s call it marketing and add it to the event_count metric, like so:
spotlight:
  categories:
    marketing:
      label: Marketing
      color: "blue"
    revenue:
      label: Revenue
      color: "orange"
Now you can add the marketing category to the event_count metric: 
models:
  - name: events
    meta:
      spotlight:
        visibility: show
        categories:
          - revenue
    metrics:
      - name: event_count
        type: count
        spotlight:
          categories:
            - marketing
In this example, the event_count metric will have both the marketing and revenue categories, it’s cumulative.
  1. Once you compile your project, you’ll see the event_count metric in the catalog with both the marketing and revenue categories and you can use this to filter your metrics in the catalog.
The categories you define need to be unique, so you can’t have two categories with the same name.If you try to add a category with the same name as an existing category, you’ll get an error. This error will be displayed in the UI and in the terminal (if you use the Lightdash CLI) when you compile your project.

​
Configuring default time settings in .yml

We recommend setting up default time fields to make it easier for your business users and save them time. To pre-select a time field in the explore view, simply define the default settings in your Lightdash .yml files.

​
Set a table-level default time dimension

  1. Create or modify your table configuration in the .yml file. For example, to set a default time dimension on the events table:
models:
  - name: events
    columns:
      - name: event_date
        description: "Event date"
        meta:
          dimension:
            label: "Event date"
            type: date
            time_intervals:
              - DAY
      - name: event
        description: "Event"
        meta:
          dimension:
            type: string
          metrics:
            count:
              type: count
  1. Add the default time dimension at the table level:
models:
  - name: events
    meta:
      default_time_dimension:
        field: event_date
        interval: DAY
    columns:
      # ... your column definitions here
  1. Compile your project
  2. Navigate to the metrics catalog
  3. Open any metrics from the events table
  4. All metrics with that default time set will be plotted against the event date with day granularity in the last 30 days

​
Set a metric-level default time dimension

This will override the time dimension defined on the table level.
  1. Modify your existing table configuration to add a metric-level default time dimension:
models:
  - name: events
    meta:
      default_time_dimension:
        field: event_date
        interval: DAY
    columns:
      - name: event
        description: "Event"
        meta:
          metrics:
            count:
              type: count
              # This will override the table level default time dimension
              default_time_dimension:
                field: event_date
                interval: MONTH
  1. Compile your project
  2. Navigate to the metrics catalog
  3. Explore the Events’ count metric
  4. The metric will be plotted against the event date with month granularity, instead of the default day granularity applied to the table

​
Canvas view (alpha)

The Canvas View is a powerful, flexible workspace designed for visualizing and organizing metrics in creative ways. A key use case is creating Metric Trees to visualize metric relationships, hierarchies, and dependencies. This visualization enables you to see how metrics impact your KPIs and compare performance over the previous month.

​
How to use the ‘Canvas view’ for Metric trees:

  1. Filter your metrics: Use the ‘categories’ or ‘search’ functions to narrow your list of metrics. Canvas view currently works best with fewer than 30 metrics to ensure smooth performance. Need help creating categories? Learn more here.
  2. Enable Canvas view: Select Canvas view to activate the workspace.
  3. Add metrics: Drag your desired metrics from the grey sidebar into the canvas workspace.
  4. Create connections: Link metrics by dragging between nodes to build relationships and dependencies. Connected nodes will be saved and visible the next time you filter your metrics down by category.
  5. Remove nodes: Select a node and press Backspace to delete it.
  6. Permissions: Viewers can see trees created in the Canvas View but cannot make edits.
Canvas view is currently in alpha. Your metric connections are saved, so the next time you filter by a category and switch to canvas view, you’ll see your saved connections. However, the placement of any unconnected tiles will not be retained.

​
FAQs

a. What time intervals are supported? Currently, we only support: DAY, WEEK, MONTH, YEAR b. What pre-filled filters are applied?
  • Time grain Year -> past 3 years
  • Time grain Month -> past 12 months
  • Time grain Week -> past 12 weeks
  • Time grain Day -> past 30 days
So if one of your business users explores a metric with a default time grain of DAY, metrics will be shown for the past 30 days with granularity of days with the default time dimension prefilled. c. Can I pull through other metadata from my .yml files? Not yet, but soon you’ll be able to manage metadata directly in the UI and sync it back to dbt. d. Which other metrics can I compare my selected metric by?
  1. Metrics with defaults in .yml: Metrics with a default time dimension specified in the .yml file will always appear.
  2. Metrics with a single time dimension: Metrics from tables with only one time dimension will appear as it’s assumed to be the most relevant.
  3. Metrics from joined tables: Metrics from joined tables that meet the criteria in points 1 and 2 will also appear.
e. How can I be sure that my yml changes are correct? If you use VSCode, you can use our Lightdash schema validation to check your yml files are correct.
  1. Install this YAML extention for VSCode: https://marketplace.visualstudio.com/items?itemName=redhat.vscode-yaml
  2. Open you user settings in JSON format and add the following: 
"[yaml]": {
  "editor.defaultFormatter": "redhat.vscode-yaml"
},
"yaml.schemas": {
  "https://raw.githubusercontent.com/lightdash/lightdash/refs/heads/main/packages/common/src/schemas/json/lightdash-dbt-2.0.json": [
    "*.yml",
    "/**/models/**/*.yml",
    "/**/models/**/*.yaml",
    "!lightdash.config.yml",
    "!dbt_project.yml"
  ],
  "https://raw.githubusercontent.com/lightdash/lightdash/refs/heads/main/packages/common/src/schemas/json/lightdash-project-config-1.0.json": [
    "lightdash.config.yml"
  ]
}
This will add schema validation to your model yml files and your lightdash.config.yml file.
  1. Reload VSCode
  2. You’ll see a red squiggly line under any errors in your yml files as well as suggestions for how to fix them and what is allowed.

​
Roles and permissions

ActionProject AdminProject DeveloperProject EditorProject Interactive ViewerProject Viewer
Browse the ‘Metrics catalog’
Add/edit /delete ‘Categories’
Open the ‘Metrics Explorer’