> ## Documentation Index
> Fetch the complete documentation index at: https://wiki.darknetsearch.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Monitoring assets

> Watch your assets continuously — create monitoring rules, read and triage matches, suppress noise, and track the numbers.

# Monitoring assets

A search answers a question \*now\*. \*\*Monitoring\*\* keeps asking it for you: you hand the platform an asset to watch — a domain, a brand, a query — and it re-runs the search on a schedule, recording every new hit and notifying you. (In the dashboard this is the \*\*Alerts\*\* section.)

#### How it works

Monitoring is built from a few pieces that fit into a loop:

1. A **monitoring rule** ties one **data source** to one **asset**. The data source is an *alert service* — Telegram, leaked credentials, phishing, certificates, ransomware, and the rest of the catalog. The asset is the rule's `args` — the domain, brand, or query you want watched.
2. The platform runs the rule on its **schedule**. Each run searches that source for hits **new since the rule last ran** — so you only ever see fresh exposures.
3. New hits are recorded as a **match** (an *incident* in the dashboard) and **delivered** to your email recipients and/or a webhook.
4. You **read and triage** matches, **export** them, and **suppress** the false positives with an **exclusion list**.
5. **Metrics** roll it all up — how much is hitting, on which sources, over time.

#### Set it up

Pick a data source, give it your asset, set how often it runs, and attach delivery. → [Create a monitoring rule](https://github.com/kaduu-cti/darknetsearch-docs/blob/main/api/guides/monitoring-rules/README.md)

Configure the email senders, recipients, and templates — or a webhook — that matches are sent to. → [Delivery: email and webhooks](https://github.com/kaduu-cti/darknetsearch-docs/blob/main/api/guides/monitoring-delivery/README.md)

List incidents, open one, page its hits (the shape depends on the source), triage, and export. → [Read and triage matches](https://github.com/kaduu-cti/darknetsearch-docs/blob/main/api/guides/monitoring-matches/README.md)

Build a per-rule exclusion list — by hand or by uploading a CSV — to suppress known-good results. → [Exclusion lists](https://github.com/kaduu-cti/darknetsearch-docs/blob/main/api/guides/monitoring-exclusions/README.md)

Pull the overview, the monthly distribution, and per-service hit counts. → [Metrics](https://github.com/kaduu-cti/darknetsearch-docs/blob/main/api/guides/monitoring-metrics/README.md)

Every endpoint in this section is tagged **alert-system** in the [API reference](https://client-api.leak.center/scalar-docs/) and is org-scoped — calls resolve to your organization automatically.