> For the complete documentation index, see [llms.txt](https://docs.luciq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.luciq.ai/common-tasks/set-up-and-tune-alerts.md).

# Set up and tune alerts

Set up Luciq alerts for crashes, stability, and performance, then cut the noise, from the dashboard, your AI client, the CLI, or agent skills.

Get told when crash-free rates drop, a new crash appears, or a network call starts failing. Then find what your alerts miss and quiet the ones that fire too often.

You can do this from any surface. Each one works with the same alert rules, so a rule you create from your AI client shows up in the dashboard, and the other way around.

{% hint style="info" %}
Every new app environment already has [predefined alerts](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/predefined-alerts.md) for crash-free rates, crashes, and key performance metrics. Start by reviewing those.
{% endhint %}

## Create an alert

{% tabs %}
{% tab title="Dashboard" %}

1. Open **Alerts & Rules** from the Luciq menu and click **Create**.
2. Pick what to watch: crash-free sessions or users, crashes (first seen, regression, or spike), network failures, a performance metric such as app launch or screen loading, bug reports, or a rollout.
3. Add conditions to narrow it down, such as app version, failure type, or threshold.
4. Choose where to send it: email, Slack, Microsoft Teams, or an integration such as [PagerDuty](/product-guides-and-integrations/integrations/pagerduty.md), [Opsgenie](/product-guides-and-integrations/integrations/opsgenie.md), or a [webhook](/product-guides-and-integrations/integrations/webhook.md). The channels available depend on the alert type.

Step-by-step guides for each alert type:

* [Crash-free rates](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/alerting-for-app-stability-crash-free-rates.md)
* [Crashes](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/alerting-for-crash-reporting.md) and [accelerating crashes](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/automatic-detection-for-accelerating-crashes.md)
* [Performance metrics](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/alerting-for-performance-metrics.md) and [network failures](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/network-failure-alerts.md)
* [Bug reports](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/alerting-and-automation-for-bug-reporting.md)
* [Rollouts](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/alerting-and-automation-for-rollout-management.md)
  {% endtab %}

{% tab title="AI client" %}
Connect your AI client to the [Luciq MCP Server](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/getting-started.md), then ask in plain language:

> "Create an alert when crash-free sessions drop below 99.5% on the latest release."\
> "Alert me when the ANR rate goes above 1%."

The agent reads your app's alert building blocks first, then creates the rule from them. It confirms with you before it changes anything. It uses the `read_alerts` and `write_alerts` tools, described under **Alerts & Rules** in the [MCP Tools Reference](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/mcp-tools-reference.md).
{% endtab %}

{% tab title="CLI" %}
Show the building blocks for your app, then create the rule from them:

```bash
luciq alerts init --slug my-app --mode production
luciq alerts create --slug my-app --mode production --payload '{"title":"…", …}'
```

Use `luciq alerts list`, `show`, `update`, and `delete` to manage existing rules. Full options are in the [CLI Command Reference](/product-guides-and-integrations/product-guides/luciq-cli/command-reference.md).
{% endtab %}

{% tab title="Agent skills" %}
Ask your AI client to set up an alert, and the [`luciq-alert-config`](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-alert-config.md) skill walks it through the job step by step, without guessing values.

If you use the Luciq MCP Server, you already have the skills. Nothing to install. See [Agent Skills](/product-guides-and-integrations/product-guides/ai-features/agent-skills.md).
{% endtab %}
{% endtabs %}

## Find what your alerts miss

A gap is a metric that is unhealthy or important and has no alert watching it.

{% tabs %}
{% tab title="AI client" %}

> "Am I missing any alerts?"\
> "What should I be alerting on for this app?"

The [`luciq-alert-gaps`](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-alert-gaps.md) skill compares your live metrics with your existing rules and proposes alerts that close the gaps.
{% endtab %}

{% tab title="Dashboard" %}
Review your rules in **Alerts & Rules**, and use [Copying Alerts & Rules](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/copying-alerts-and-rules.md) to reuse a good set of rules across your other apps and environments.
{% endtab %}
{% endtabs %}

## Cut the noise

An alert is noisy when it fires often and the firings are not worth a notification each.

{% tabs %}
{% tab title="AI client" %}

> "My alerts are too noisy."\
> "Which alerts fire too often?"

The [`luciq-alert-noise`](/product-guides-and-integrations/product-guides/ai-features/agent-skills/luciq-alert-noise.md) skill finds the rules that fire too often and fixes them at the source, without cutting coverage.
{% endtab %}

{% tab title="Dashboard" %}
Open [Triggered Alerts](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules/triggered-alerts.md) to see each firing, when it happened, and the conditions that triggered it. Tighten the thresholds or conditions of the rules that fire most.
{% endtab %}

{% tab title="CLI" %}
List your rules by how often they fire:

```bash
luciq alerts list --slug my-app --mode production --sort-by highest_triggered_count
```

`luciq incidents list --sort-by count` shows which firings repeat most. See the [CLI Command Reference](/product-guides-and-integrations/product-guides/luciq-cli/command-reference.md).
{% endtab %}
{% endtabs %}

## Related

* [Alerts & Rules](/product-guides-and-integrations/product-guides/automation-and-workflows/alerts-and-rules.md): every alert type in detail
* [Team Ownership](/product-guides-and-integrations/product-guides/automation-and-workflows/team-ownership.md): send alerts to the team that owns the code
* [Manage Alerts and Rules](/product-guides-and-integrations/product-guides/ai-features/luciq-mcp-server/use-cases-and-workflows.md) in the MCP Use Cases & Workflows


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.luciq.ai/common-tasks/set-up-and-tune-alerts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.