> For the complete documentation index, see [llms.txt](https://doc.commandersact.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.commandersact.com/features/sources/overview.md).
# Sources Overview
## What is a source ?
A source is an emitter of events, more information [here](/getting-started/concepts.md#source).
## Source list
In *Sources / Overview*, you will find the full list of sources already configured.
You can search a source by name and filter on environment (production, staging, ...), status (active or inactive) and per destination
You can easily edit a source by clicking its name or the pencil icon.
{% hint style="info" %}
**Web containers** are special client-side sources, when editing them you will be redirected to dedicated interfaces
{% endhint %}
## Trend and data quality
The trend represents the evolution of number of events received on the last month.
The data quality indicator allows to quickly visualize the status of the source, if data are of good quality (
) or not (
) on the last hour.
The quality score of events is represented by a weather icon:
* sunny if the percent of correct events is equal to 100%
* 
cloudy between 95% and 99.99%
* 
rainy between 90 and 95%
* stormy below 90%
---
# 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://doc.commandersact.com/features/sources/overview.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.