# 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](https://docs.dbnl.com/v0.27.x/configuration/data-pipeline). 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](https://docs.dbnl.com/v0.27.x/workflow/explorer) or inspection of [Logs](https://docs.dbnl.com/v0.27.x/workflow/logs) and track as [Metrics](https://docs.dbnl.com/v0.27.x/workflow/metrics) or [Segments](https://docs.dbnl.com/v0.27.x/workflow/segments).

<figure><img src="https://content.gitbook.com/content/8N8zzLtIch6ZiTSwWtXD/blobs/shsHnuemY98UmZM1xrqc/image.png" 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](https://docs.dbnl.com/v0.27.x/workflow/status) 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