Saved views
Save and reuse filtered Infrastructure Explorer views to stay focused on the work that matters. A saved view preserves the current configuration so you can return to a workflow without reapplying settings each time.
Infrastructure Explorer saved views are part of the Saved Views shared component used across Coralogix products. The core experience is the same in each product; the options that get saved differ.
What an Infrastructure Explorer saved view captures
| Option | Description |
|---|---|
| Query | The current search query and dataset |
| Filters | The applied filters |
| Table settings | The column layout and formatting |
| Widget state | The current grouping shown in Overview widgets |
| Time range | The selected time range, with optional Lock time to fix the range |
| Set as default view | Makes this the default landing view in Infrastructure Explorer |
The Fields option, available in Cases and Explore, does not apply in Infrastructure Explorer.
Create a saved view
In Infrastructure Explorer, the saved view also captures the Widget state option, the current grouping shown in Overview widgets.
Use saved views
Saved views are accessed via the All views link in the top-left corner of Infrastructure Explorer. The active view name appears next to Infrastructure Explorer at the top of the page.
- Select All views to open the saved views panel.
- Find views under Recent or All views.
- Use Search saved views to locate a view by name.
- Select a saved view to apply it.
Update or save as new view
When a loaded view has unsaved changes, the Save view menu provides:
- Update current view: Save the changes to the loaded view.
- Save as new view: Save the changes as a new view, leaving the original unchanged.
Edit, clone, or delete a saved view
Share a saved view
To share a saved view with a teammate, copy the page URL after the saved view is loaded. Opening the URL applies the same query, filters, table settings, and time range.
Set the team default view
Admins can set a team-level default view so every team member lands on the same Infrastructure Explorer configuration by default. Individual users can still override the team default for themselves.
To set the team default:
- Open Settings and navigate to the Infrastructure Monitoring section.
- Under Team default view, select an existing saved view from the dropdown.
- Select Save.
To override the team default for your own account, load any saved view and enable Set as default view in the Save view panel. Your personal default takes precedence over the team default.
The team default applies to the main Infrastructure Explorer screen. Resource type pages, such as Pods or Hosts, do not take their own team default.
This feature requires the INFRA-TEAM-DEFAULT-VIEWS:MANAGE permission, included only in the Platform Admin system role by default. Team members need INFRA-TEAM-DEFAULT-VIEWS:READ to see the configured team default in their own settings page.
Access policy
For the cross-product model, examples, and FAQs, see the access policies overview.
Permissions
To view and manage saved views in Infrastructure Explorer, your role needs the following permissions.
| Resource | Description | System roles | API presets |
|---|---|---|---|
INFRA-SAVED-VIEWS:MANAGE | Create, edit, and delete saved views in Infra Explorer. | Data Admin, Observability Lead, Platform Admin, Read-Only User, Security User, Standard User | - |
INFRA-SAVED-VIEWS:READ | View saved views. | Data Admin, Observability Lead, Platform Admin, Read-Only User, Security User, Standard User | - |
INFRA-SAVED-VIEWS:READACCESSPOLICY | View access policies defined on saved views. | Data Admin, Observability Lead, Platform Admin, Security User | - |
INFRA-SAVED-VIEWS:UPDATEACCESSPOLICY | Manage access policies on Infra Explorer saved views. | Data Admin, Observability Lead, Platform Admin, Security User | - |
INFRA-TEAM-DEFAULT-VIEWS:MANAGE | Define team-level default views in Infra Monitoring settings. | Platform Admin | - |
INFRA-TEAM-DEFAULT-VIEWS:READ | View team-level default views. | Platform Admin | - |
Building a policy also requires TEAM-GROUPS:READCONFIG to select target groups. See the permissions list for the role assignments per key.