> 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/previous-versions/sb-5.0-version/learn/product-and-developer-guide/summarisers.md).

# Summarisers

A generic summariser is generated from the telemetry events to enable easier access of frequently accessed metrics. For e.g., session level summaries or content player level summaries are some of the frequently accessed metrics derived for an actor/user. The content player level metrics can possibly be used to compute the total time spent by the user by playing various content in the platform across multiple sessions in a day.

```
app start
  session start
  ____
    workflow start (course start)
    ____
    ____
      play start
      ____
      ____
      play end
      ____
      play start
      ____
      ____
      play end
    ____
    ____
    workflow end
  ____
  session end
app end

Summary counts:
- App Summaries: 1
- Session Summaries: 1
- Workflow Summaries: 1
- Player Summaries: 2
```

#### Key Features:

1. Frequently used metrics: The generic summariser generates some of the frequently used metrics which can be used to generate custom data products for deriving various insights.
2. Data size reduction: Custom data products need to traverse huge amount of data to derive insights if they were to operate on the raw telemetry events generated from various devices. The summariser reduces the data traversal to almost 1/100th by summarising the data at a device level. This reduces the computation time and resources as well.

{% embed url="<https://github.com/project-sunbird/sunbird-core-dataproducts>" %}
Data Products source code
{% endembed %}


---

# 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://obsrv.sunbird.org/previous-versions/sb-5.0-version/learn/product-and-developer-guide/summarisers.md?ask=<question>&goal=<user_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.