> For the complete documentation index, see [llms.txt](https://docs.transparentedge.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.transparentedge.eu/security/anomaly-detection.md). # Anomaly Detection The anomaly detection system is a valuable tool that analyzes patterns and identifies disruptions in your website traffic, alerting you when they occur and providing the option to trigger our systems to react to an incident when necessary. All our solutions include the option for monitoring a single site. If you wish to enhance the security of additional sites, we recommend contacting . ## How to activate After accessing [the dashboard](https://dashboard.transparentcdn.com/auth/login), go to the 'Anomaly Detection' section. It is highly likely that the monitored sites and detection history will be empty. The 'New' button, located within the monitored sites, will allow you to create a new configuration.

When you click it, a modal will open in which you will select the site and service for which you want to configure anomaly detection. After this, the **types of anomalies and thresholds** will appear. A threshold is a fixed value or a percentage of the total requests. This limit indicates when an anomaly is considered to occur if the metric we are observing exceeds the specified value. All parameters of the anomalies can only be modified if the service has been contracted, although a set of them is available in the *freemium* version. Once the configuration has been created and saved, activating anomaly detection will be as simple as checking the box found in the dropdown menu of that site.

Remember that you can always go back and modify that configuration directly from the 'Settings' button, also present in the site's dropdown menu.
{% content-ref url="/pages/OaUfXf8bjiacVsZRAEWJ" %} [Detection Types](/security/anomaly-detection/detection-types.md) {% endcontent-ref %} {% content-ref url="/pages/FqbWlDWdp8XIUFI36hq8" %} [Automatic Reactions](/security/anomaly-detection/automatic-reactions.md) {% endcontent-ref %} {% content-ref url="/pages/gUsdBKPe1bQJRldjheZJ" %} [Detection History](/security/anomaly-detection/detection-history.md) {% endcontent-ref %} --- # 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.transparentedge.eu/security/anomaly-detection.md?ask=&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.