> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/trendseeker/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/trendseeker/technical-docs/trendseeker-correlations.md).

# TrendSeeker Correlations

{% hint style="info" %}
A TrendSeeker Correlation is the parent record that ties together all parts of a detected trend. Created via [TrendSeeker Rules](/trendseeker/technical-docs/trendseeker-rules.md), the correlation record contains a synopsis and analysis of the detected trend.

In addition, TrendSeeker Links relate the associated TrendSeeker Rule, all Detected records that are part of the trend, and all Created records as a result of the trend detection.
{% endhint %}

<figure><img src="/files/HXST5KzcNhUjflK3LbRM" alt=""><figcaption><p>TrendSeeker Correlation</p></figcaption></figure>

* **Description**: Description of the specific metrics, aggregates, timing, and threshold that resulted in the creation of the TrendSeeker Correlation.
* **Analysis**: [AI analysis](/trendseeker/technical-docs/getting-started/setting-up-an-ai-connector.md) of the records associated with the TrendSeeker Correlation. Based on the configuration of the associated TrendSeeker Rule, AI will analyze specific fields from the related records in order to find commonalities, root cause, and potential solutions.

### Intelligence

{% hint style="info" %}
In order to utilize AI Intelligence, you must first configure an [AI Connector](/trendseeker/technical-docs/getting-started/setting-up-an-ai-connector.md).
{% endhint %}

The intelligence tab provides details about AI analysis, and provides the opportunity to tweak details of AI input in order to re-analyze the correlation to best facilitate troubleshooting & resolution.

* **Analyze findings?**: Choose whether to use AI for analysis.
* **Detection table fields**: Choose the fields from the related records that you wish to send to AI during analysis.
* **Prompt**: To be sent to the AI engine, specific instructions and questions to ask about underlying records in order to best analyze the correlation.
* **AI request**: The underlying AI request, where you can view the specific payloads and AI query parameters

<figure><img src="/files/ecvXDIRuqhqkWOyaR1Mt" alt=""><figcaption><p>TrendSeeker Links</p></figcaption></figure>

The TrendSeeker Links related list ties together the [TrendSeeker Rule](/trendseeker/technical-docs/trendseeker-rules.md), Detected records, and any Created records that are part of the correlation. This makes it simple to understand the Correlation and navigate to related records.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yansalabs.com/trendseeker/technical-docs/trendseeker-correlations.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.