---
title: Align your teams with workloads
source: https://docs.newrelic.com/docs/tutorial-peak-demand/organize-data-workloads
---

To start from a strong position on gameday, we recommend creating workloads during the planning phase. Beyond application health and resource allocation, the choreography of a gameday depends on data alignment and strong communication. Workloads let you customize how you experience the data reported to New Relic. You can create workloads around events, teams, or responsibilities—anything that fits your particular needs. Once created, workloads let you view aggregated health and activity data from frontend to backend services across your entire system.

![Workload_health_tab](https://docs.newrelic.com/images/workloads_screenshot-full_workload-health-tab.webp "Workload_health_tab")

## Objectives [#objective]

This tutorial gives a primer on using workloads for a peak performance day. You will:

-   Create your first workload
-   Customize your workload for your gameday event

## Create a workload for game day [#create]

To get started with workloads, go to **[one.newrelic.com > Workloads](https://one.newrelic.com/workloads)**, then click **Create a workload**.

![Add your sources to the workload](https://docs.newrelic.com/images/apm_screenshot-crop_add-sources-to-workload.webp "Add sources to workload")

### Create your first workload

The **Create a workload** page lists data sources from all the accounts you have access to. If there's a capability, service, component, or resource that's reporting to New Relic, you can add it to a workload.

To create a workload:

1.  Select the account that owns the workload.
2.  Name your workload, something like `Peak Demand Data` or anything else meaningful to your team.
3.  Query for the sources that you want represented in your workload.

### Choose data sources for your workload

To get the most out of workloads, we recommend you add:

-   APM services, hosts, service levels, synthetic monitors, load balancers, Kubernetes pods or even other workloads.
-   `log` to your workloads query for easy access to the logs UI page.
-   Relevant dashboards to a workload, such as a dashboard that only displays your KPIs, or a dashboard of business critical transactions.

### Add data source to your workload

Once you've whittled down your selection, you have two options for adding a data source to a workload. Both do slightly different things.

-   **Add** adds the source in a static state. For example, if you added a dashboard at 10am, but added more widgets to that dashboard at 11am, those additional widgets wouldn't appear in the workload.
-   **Add this query** adds the entity dynamically. Using the same dashboard example, the 11am changes (and any future changes) would automatically appear in the workload.

### Add dashboards to your workload

If you have custom dashboards and you already know which data is relevant to your team, you can link those dashboards from your workload. You can also set filters on dashboards to scope them to a workload-specific context. When you select that dashboard from the workload, it opens with the filter already applied.

![New Relic workloads - add dashboards](https://docs.newrelic.com/images/workloads_screenshot-full_workloads-dashboard-entities.webp "new-relic-workloads-add-dashboards.png")

**[one.newrelic.com > All capabilities](https://one.newrelic.com/all-capabilities) > Apps > Workloads**: You can add dashboards to a workload.

## Using workloads on gameday [#gameday]

Your workloads are your gameday's ground zero. On gameday, everyone on your team—regardless of their role—should start at the same workload and refer back to it when communicating about alert events. By aligning your team around the same sets of data, you avoid miscommunications and allow them to resolve outages faster.

[Get started](https://docs.newrelic.com/docs/journey-demand/get-started)

Get data about your architecture with APM and infrastructure agents

[Create service levels for gameday](https://docs.newrelic.com/docs/journey-demand/find-your-baseline/)

Create service levels informed by your baseline

[Reduce noise with quality alerts](https://docs.newrelic.com/docs/journey-demand/create-quality-alerts/)

Evaluate your alerts with alert quality management

[Align your teams with workloads](https://docs.newrelic.com/docs/journey-demand/organize-data-workloads/)

Align your teams around the same data

[Autoscale your infrastructure with Kubernetes](https://docs.newrelic.com/docs/journey-demand/autoscale-your-infra/)

Scale your resources as demand peaks