> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/investigate/insights.md). # Insights Quickly understand your data with groundcover groundcover insights give you a clear snapshot of notable events in your data. Currently, the platform supports **Error Anomalies**, with more insight types on the way.

Logs Insights

#### Error Anomalies Error Anomalies instantly highlight workloads, containers, or environments experiencing unusual spikes in **Error or Critical logs**, as well as **Traces marked with an error status**. These anomalies are detected using statistical algorithms, continuously refined through user feedback for accuracy. Each insight surfaces trends based on the entity’s error signals (e.g., workload, container, etc.): On **Logs**, anomalies are based on logs filtered by `level:error` or `level:critical`, and grouped by: * `workload` * `container` * `namespace` * `environment` * `cluster` On **Traces**, anomalies are based on traces filtered by `status:error`, and grouped by a more granular set of dimensions: * `protocol_type` * `return_code` * `role` (client/server) * `workload` * `container` * `namespace` * `environment` * `cluster` --- # 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.groundcover.com/investigate/insights.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.