> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/mgramseva/introducing-mgramseva/platform/technical-user-docs/backend-services/mgramseva-rollout-dashboard.md).

# mGramSeva - Rollout Dashboard

## O**bjective**

The purpose of the mGramSeva Rollout Dashboard Scripts to aggregate the data points from mgramseva DB and services for Rollout dashboard in Metabase.

## Overview <a href="#overview" id="overview"></a>

mGramSeva Rollout Dashboard is a python script for pushing the data from the mGramSeva to a specific table in DB on a daily basis which can be loaded to Metabase and graphical dashboard built on top of this table in the Metabase.

## Pre-requisites <a href="#pre-requisites" id="pre-requisites"></a>

Before you proceed with the configuration, make sure the following pre-requisites are met -

* *Python 3.9*
* mGramSeva DB
* mGramseva user details who has access to MDMS service API
* mGramSeva mdms service access

## Key Functionalities <a href="#key-functionalities" id="key-functionalities"></a>

* Collecting the data on certain data points and inserting the data into the rollout dashboard table in the DB\
  User Story with details of the data point: [![](https://digit-discuss.atlassian.net/images/icons/issuetypes/story.svg)IFIX-485: \[1.0.1\] Rollout Dashboards on MetabaseQA SIGNOFF](https://digit-discuss.atlassian.net/browse/IFIX-485)

## Deployment Details <a href="#deployment-details" id="deployment-details"></a>

Please deploy the following build.

* **rollout-dashboard-cronjob:develop-2a8d6a44-3**

## Integration <a href="#integration" id="integration"></a>

### Integration Scope <a href="#integration-scope" id="integration-scope"></a>

mGramSeva Rollout Dashboard is not directly integrated with any of the services except this scripts fetch the data from the MDMS service and mGramSeva DB

1. Configure the username, tenantId and password of the user for which mdms service access is available on the environment specific yaml file in DevOps. Example below\
   [<img src="https://github.com/fluidicon.png" alt="" data-size="line">iFix-DevOps/mgramseva-qa.yaml at e471be940b88ccd8811b2dfb7a0e4187b0ec39cd · misdwss/iFix-DevOps](https://github.com/misdwss/iFix-DevOps/blob/e471be940b88ccd8811b2dfb7a0e4187b0ec39cd/deploy-as-code/helm/environments/mgramseva-qa.yaml#L224)

### Steps to run locally <a href="#steps-to-run-locally" id="steps-to-run-locally"></a>

please follow the steps below

[<img src="https://github.com/fluidicon.png" alt="" data-size="line">punjab-mgramseva/LOCALSETUP.md at master · misdwss/punjab-mgramseva](https://github.com/misdwss/punjab-mgramseva/blob/master/utilities/rollout-dashboard-cronjob/LOCALSETUP.md)

### Loading to Metabase <a href="#loading-to-metabase" id="loading-to-metabase"></a>

The python script inserts the data into table “`roll_out_dashboard`“ in mgramSevaDb for every run, it cleans the old data and creates new data.

This table has to be loaded into the metabase by adding mGramSeva DB to the metabase.

> [![Creative Commons License](https://i.creativecommons.org/l/by/4.0/80x15.png)*​*](http://creativecommons.org/licenses/by/4.0/)*All content on this page by* [*eGov Foundation*](https://egov.org.in/) *is licensed under a* [*Creative Commons Attribution 4.0 International License*](http://creativecommons.org/licenses/by/4.0/)


---

# 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.digit.org/mgramseva/introducing-mgramseva/platform/technical-user-docs/backend-services/mgramseva-rollout-dashboard.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.