> For the complete documentation index, see [llms.txt](https://obsrv.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://obsrv.sunbird.org/readme.md). # Welcome to Obsrv Obsrv was conceived and incubated within the open-source initiative [Sunbird](https://sunbird.org/) in 2016. Obsrv is built to operate with highest levels of reliability with bare minimum operations effort at scale. One of the early and significant applications of Obsrv is within **DIKSHA**, the national platform for schools and teachers in India. In the DIKSHA environment, Obsrv handled data volumes ranging from a few million events per day to **2 billion events per day** at peak. The current average volume is 500 million events per day and the system has not experienced any downtime in the past 2 years. This microsite provides a comprehensive overview and guides to understand and use Obsrv for various data use cases. ## Getting Started
IntroductionIntro to Obrsvintro-2-card.jpgThe Value of Data
Core ConceptsUnderstand Obsrv Fundamentalsconcepts-card.jpgCore Concepts
Case StudiesReal World Use casescase-studies-card.jpgCase Studies
## Guides
InstallationInstallation Guideinstallation-card.jpg
APIsAPI SpecificationAPI-card.jpg
Developer GuideDeveloper Guideguide-card.jpg
--- # 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://obsrv.sunbird.org/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.