---
title: "Save a log view"
description: "Save filters, sorting, and column layouts for repeatable trace, span, and session investigations."
sidebar:
  label: "Save a log view"
seo:
  title: "Save a Log View | Judgment How-to"
  description: "Create private or shared log views, update or duplicate them, and choose your default view in Judgment."
---

Save a view when you regularly return to the same population of traces, spans,
or sessions. Views belong to a project and a Logs tab. They store the table
configuration, not a frozen set of results.

## Prerequisites

- Access to the project and its **Logs** page
- Filters and columns that answer a repeatable investigation question
- Developer access or higher to create or change a **Shared** view

Any project member can create a **Private** view. Only the author can edit or
delete a saved view, including a shared one; administrator access does not
make another person's view editable.

## Create a view

1. Open **Logs > Traces**, **Spans**, or **Sessions** and set your filters.
2. Choose the sort and arrange the columns you want to reuse.
3. Open **Views** (or the currently selected view's name) and select **New view**.
4. Enter a **Name** and optional **Description**. Choose **Private** for your
   own use or **Shared** for everyone with access to this project.
5. Select **Create view**. Confirm the saved name appears as the active view.

For example, save a traces view named `Slow checkout calls` with a recorded
operation-name filter and a duration threshold. Describe the threshold and
investigation purpose so a teammate understands the selection.

## Know what is saved

| Included | Separate from the view |
| --- | --- |
| Filters, including a Traces **Full Text Search** filter | The selected time window |
| Sort field and direction | The records currently returned |
| Column order, visibility, and widths | Selected rows and the open trace or session |
| Trace attribute-column selection | Project access permissions |

Recheck the time selector every time you apply a view. New traffic can change
the results even when the saved configuration is unchanged. Use a dataset
when you need to preserve particular examples.

## Apply and update a view

Open the view menu and choose a **Private** or **Shared** entry. After changing
its filters, sorting, or column configuration, the control marks unsaved
changes. Choose the action that matches your intent:

| Action | Result |
| --- | --- |
| **Save changes** | Updates the active view you own. People using a shared view will use the updated configuration. |
| **Save as new view** | Creates a separate named view from the current configuration. Use this to adapt someone else's view. |
| **Discard changes** | Restores the active view's saved configuration. |

The adjacent **Save** or **Save as…** button provides a shortcut when changes
are present. Switching or clearing a view can ask you to discard unsaved
changes; save first if you want to keep them.

The built-in **All traces**, **All spans**, and **All sessions** entries are
starting points. They cannot be renamed, overwritten, or deleted. Choose
**New view** or **Save view** to retain a configuration based on one of them.

## Choose your default

In the view menu, use the pin control labeled **Set as default view** on a
saved view. A **Default** marker confirms the selection. Use **Remove default
view** to clear your preference.

The default is personal and applies to this project and Logs tab. It does not
change anyone else's default. A link that already specifies a view, filters,
sorting, or search takes precedence over your default preference.

## Share, rename, or remove a view

Use **Edit view** on a view you own to change its name, description, or
**Private / Shared** visibility, then select **Save changes**. Sharing makes
the configuration available to project members; it does not make the project
or its logs public.

Choose **Delete view** and confirm **Delete** to remove a view you own. This
deletes the saved configuration, not the underlying traces, spans, or sessions.
Use **Clear view** to leave a view without deleting it.

<span id="verify-and-troubleshoot" />

## Troubleshooting

- If **Save changes** is unavailable, check authorship. Save a new view to
  keep your variation of someone else's configuration.
- If sharing fails, check your organization role; shared-view writes require
  developer access or higher even when the picker is visible.
- If a view is missing, check the project and tab, whether it is private to
  someone else, and whether its author removed it or changed its visibility.

## Next step

Use the saved population to [investigate a failed
trace](/documentation/monitoring/trace-investigation) and preserve a concrete
regression case.