> For the complete documentation index, see [llms.txt](https://docs.dbnl.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dbnl.com/v0.27.x/workflow/insights.md).

# Insights

An Insight is a human readable explanation and quantification of behavioral signals generated from unsupervised analysis of enriched logs as part of the [Data Pipeline](/v0.27.x/configuration/data-pipeline.md). They are detected clusters defined by filters on Columns of log data that correspond to unique behavior.

Insights represent signals that the user can triage and refine through the [Explorer](/v0.27.x/workflow/explorer.md) or inspection of [Logs](/v0.27.x/workflow/logs.md) and track as [Metrics](/v0.27.x/workflow/metrics.md) or [Segments](/v0.27.x/workflow/segments.md).

<figure><img src="/files/jvE8a8TntiBAys8XuZJi" alt=""><figcaption></figcaption></figure>

### What to Expect

**Typical insight volume:** Most projects generate 5-20 new insights per week. Projects with stable, consistent behavior may generate fewer insights, while projects with volatile or rapidly changing behavior may generate more.

**If you see no insights:**

* DBNL requires at least 7 days of data to establish behavioral baselines
* Check the [Status page](/v0.27.x/workflow/status.md) to ensure pipeline runs are completing successfully
* Verify sufficient log volume (insights are more meaningful with hundreds of logs per day)
* Very stable systems with little variation may naturally generate fewer insights