# Working with alerts ### Label filters & saved views Effective alert management requires the ability to quickly isolate specific issues within a sea of data. By using label filters and saved views, DevOps and SRE teams can reduce noise and decrease MTTR by creating high-context environments. Whether you need to see only "Production" database alerts or a specific "Kubernetes Dev" cluster, these views allow for one-tap triage and consistent visibility across your organization. #### Filter alerts by labels Use labels to narrow down the list of alerts to specific services, environments, or clusters. 1. Navigate to the **Alerts** section in the main navigation menu. 2. Click on the **Filter** button located under the Labels header.
ilert-label-filters-01.png
3. In the Add label filter modal, select the **label key** from the first dropdown (e.g., `app`). 4. Choose an operator (e.g., `is equal to`). 5. Select or type the label value you wish to filter by (e.g., `database`). 6. Click **Add filter**. You can repeat this process to add multiple label requirements.
#### Create and manage saved filters Once you have defined your filters, you can save the configuration as a view for quick access in the future. 1. After applying your desired filters, look at the Saved filters bar. Click the **+ (plus) icon** next to the filter tabs.
2. In the Save view dialog, enter a Name for your view (e.g., `app`).
3. Select the Visibility level: * **Personal**: Only visible to you. * **Team**: Visible to members of specific teams you select. * **Public**: Available as a global view for all users in the account. 4. Click **Save**. The view will now appear as a dedicated tab in your Alerts dashboard. ### Edit or delete saved filters You can modify existing saved filters to update their configuration or remove them if they are no longer needed. 1. Locate the saved filter tab in the **Saved filters** bar. 2. Click the **three-dot icon** on the specific filter to open the actions menu.
3. Choose from the following options: * **Edit**: Update the name or visibility settings. * **Copy link**: Share a direct link to this filtered view with a team member. * **Duplicate**: Create a copy of the current filter to use as a template. * **Pin filter**: Set this view as your default when opening the Alerts page. * **Delete**: Permanently remove the saved view. ### Bulk actions Managing multiple alerts individually can be time-consuming during major outages or periods of high alert volume. ilert's bulk actions allow you to handle dozens of alerts at once. You can execute actions on multiple alerts directly from the alerts list view. 1. Select the alerts you wish to manage **by clicking the checkboxes** on the left side of each alert row. To select all alerts currently visible in your filtered view, **click the topmost checkbox** in the header row.
2. Once alerts are selected, a bulk action bar will appear above the list. Choose one of the following actions: * **Accept**: Acknowledge that you are working on the selected alerts. * **Reroute**: Shift the selected alerts to a different escalation policy. * **Resolve**: Mark the selected alerts as resolved if the underlying issue is fixed. * **Link incident**: Connect the selected alerts to an existing [incident](https://docs.ilert.com/incidents-and-status-pages/incidents) for streamlined communication. * **Merge**: Combine two or more alerts into one main alert. [Read more about merging alerts](https://docs.ilert.com/alerting/working-with-alerts/merging-alerts). {% hint style="warning" %} Please note that you cannot merge alerts that are already acting as parent alerts (contain other merged alerts). {% endhint %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.ilert.com/alerting/working-with-alerts.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.