> For the complete documentation index, see [llms.txt](https://docs.elastiflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.elastiflow.com/readme.md).
# ElastiFlow Documentation
### Welcome to the ElastiFlow Docs page!
ElastiFlow offers comprehensive network observability and security analytics by collecting and analyzing network flow & telemetry data. It provides deep insights into network performance, reliability, and security across your infrastructure by acting as a high-performance flow collector that processes data from various sources like NetFlow, IPFIX, and sFlow. This unified approach gives you a single, contextualized view of all network activity, helping you understand what's truly happening on your network.
### Helpful links
Get started with ElastiFlow using our new virtual appliance: [Quickstart Guide](/flowcoll/quickstart-guide.md)
Join our community to engage with other users and the ElastiFlow team.
* [ElastiFlow Community Forum](https://forum.elastiflow.com/)
* [ElastiFlow Community Slack](https://join.slack.com/t/elastiflowcommunity/shared_invite/zt-3ua41906f-5uM4aJSXO5vpJHlq4j8xhQ)
ElastiFlow instantly transforms your Open Data Platform into a powerful network observability platform.
---
# 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 following URL with the `ask` and `goal` query parameters:
```
GET https://docs.elastiflow.com/readme.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 `build a script that syncs our docs to a CMS` 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.
