> For the complete documentation index, see [llms.txt](https://docs.aiceberg.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aiceberg.ai/monitoring/what-is-the-monitoring-page/how-can-i-see-more-details-for-a-prompt/how-do-i-see-why-a-signal-fired-the-way-it-did-the-trace-feature.md).

# How do I see why a Signal fired the way it did? The Trace feature

## What is Trace?

One of the most powerful features in Aiceberg is the ability to see why a Signal was triggered and why it wasn't. **Trace** is the feature that powers our Signal detection without relying on generative AI models.

Incoming prompts are semantically chunked to preserve meaning and processed through our patented models to identify the most relevant samples. Those samples are then used to determine Signal results. Probability calculations are made and users can see the likelihood that the content matches specific risk Signals as well as the actual samples that contribute to the result.

Why this matters:

* Every detection can be audited and traced back to specific training examples
* Unpredictable outputs are reduced with verifiably consistent performance
* CPU-only processing means classification is fast
* Scores are based on mathematical proximity, not black box decisions, so scoring is transparent

To view Trace, tap into [prompt details](/monitoring/what-is-the-monitoring-page/how-can-i-see-more-details-for-a-prompt.md) from Monitoring and tap the Trace icon at the top.

![](/files/c33529fa65618496dbc06c3f53bfe54fc81aa16e)

Aiceberg semantically chunks long inputs, ensuring that each piece contains complete thoughts or concepts to improve retrieval accuracy and reduce noise.

Use the toggle to switch between prompt and response analysis and see any flagged Signals or detected Intent. The numbers in the Signal pills indicate the chunk in which the Signal was found.

![](/files/eb83d1d489370be0705e3ae70c411fc45c11a266)

Tapping the numbered selector above the chunk text will navigate you to that chunk. Selectors are highlighted to show where Signals occurred. Tap the Explainability chevron to show the five nearest neighbor samples that were used to determine similarity for Signals in that chunk.

![](/files/18c75d35ab3a4dc08c066b3d6472e07d21df7a68)


---

# 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.aiceberg.ai/monitoring/what-is-the-monitoring-page/how-can-i-see-more-details-for-a-prompt/how-do-i-see-why-a-signal-fired-the-way-it-did-the-trace-feature.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.