Skip to main content

The openIMIS Backend opensearch_reports reference module.

Project description

openIMIS Backend opensearch_reports reference module

Adding Environmental Variables to Your Build

To configure environmental variables for your build, include the following:

  • OPENSEARCH_HOST - For the non-dockerized instance in a local context, set it to 0.0.0.0:9200. For the dockerized instance, use opensearch:9200.
  • OPENSEARCH_ADMIN This variable is used for the admin username. (default value: admin)
  • OPENSEARCH_PASSWORD This variable is used for the admin password. (default value: admin)

How to configure documents in openimis businesss module?

To configure Django ORM models with OpenSearch documents using a noSQL approach, follow these steps:

  • Begin by creating a documents.py file within your module.
  • Inside the documents.py file, define a Document class that corresponds to your Django ORM model. For example:
from django_opensearch_dsl.registries import registry
from django_opensearch_dsl import Document, fields as opensearch_fields

@registry.register_document
class BeneficiaryDocument(Document):
   benefit_plan = opensearch_fields.ObjectField(properties={
       'code': opensearch_fields.KeywordField(),
       'name': opensearch_fields.KeywordField(),
   })
   individual = opensearch_fields.ObjectField(properties={
       'first_name': opensearch_fields.KeywordField(),
       'last_name': opensearch_fields.KeywordField(),
       'dob': opensearch_fields.DateField(),
   })
   status = opensearch_fields.KeywordField(fields={
       'status_key': opensearch_fields.KeywordField()}
   )

   class Index:
       name = 'beneficiary'  # Name of the Opensearch index
       settings = {
           'number_of_shards': 1,
           'number_of_replicas': 0
       }
       auto_refresh = True # automatically send updates and new objects to openSearch

   class Django:
       model = Beneficiary
       related_models = [BenefitPlan, Individual]
       fields = [
           'id',
       ]
       queryset_pagination = 5000
  • In the Django class, you can use the fields property to include all the fields that are present in your Django ORM model.
  • If you wish to include related fields (foreign keys), make sure to specify them in the related_models property of your Django class. Add all the foreign key fields that you want to include.
    class Django:
        model = Beneficiary
        related_models = [BenefitPlan, Individual]
        fields = [
            'id',
        ]
        queryset_pagination = 5000
  • If you want to customize the default behavior of field creation, declare the fields you wish to modify using the appropriate type. For foreign keys, use the ObjectField type.
  @registry.register_document
  class BeneficiaryDocument(Document):
      benefit_plan = opensearch_fields.ObjectField(properties={
          'code': opensearch_fields.KeywordField(),
          'name': opensearch_fields.KeywordField(),
      })
      individual = opensearch_fields.ObjectField(properties={
          'first_name': opensearch_fields.KeywordField(),
          'last_name': opensearch_fields.KeywordField(),
          'dob': opensearch_fields.DateField(),
      })
      status = opensearch_fields.KeywordField(fields={
          'status_key': opensearch_fields.KeywordField()}
      )
  • Note that TextField types are typically converted to non-aggregable fields in OpenSearch. If you require aggregable fields, use the KeywordField type.
  • By default, the auto_refresh property in the Index class should enable data to be automatically transferred on every CRUD operation managed by Django ORM. Ensure that this property is properly configured in your project.

How to initialize data after deployment

  • If you have initialized the application but still have some data to be transferred, you can effortlessly achieve this by using the commands available in the business module: python manage.py add_<model_name>_data_to_opensearch. This command loads existing data into OpenSearch.

How to Import a Dashboard

  • Locate the dashboard definition file in .ndjson format within the openimis-be_<module-name>/import_data directory.
  • Log in to your OpenSearch instance.
  • Expand the sidebar located on the left side of the page.
  • Navigate to Management and select Dashboards Management.
  • On the left side of the page, click on Saved Objects.
  • At the top-right corner of the table, click on Import.
  • A new side-modal will appear on the right side of the page. Drag and drop the file from openimis-be_<module-name>/import_data into the import dropzone.
  • This action will import the dashboards along with related charts that should be accessible on the visualization page.
  • Verify if the dashboards have been imported properly.

How to Export Dashboards with Related Objects like Visualizations in OpenSearch?

  • Log in to your OpenSearch instance.
  • Expand the sidebar located on the left side of the page.
  • Navigate to Management and select Dashboards Management.
  • On the left side of the page, click on Saved Objects.
  • At the top-right corner of the table, click on Export <N> objects.
  • Ensure that you have selected dashboards only. Additionally, choose the option to include related objects, and then click export all.
  • You should have downloaded file in .ndjson format.
  • Save file in the business model for initialization after deployment in openimis-be_<module-name>/import_data.
  • Rename filename into opensearch_<model-name>_dashboard.ndjson

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

openimis_be_opensearch_reports-1.1.1.tar.gz (20.8 kB view details)

Uploaded Source

Built Distribution

File details

Details for the file openimis_be_opensearch_reports-1.1.1.tar.gz.

File metadata

File hashes

Hashes for openimis_be_opensearch_reports-1.1.1.tar.gz
Algorithm Hash digest
SHA256 75fa485a374a9f731e524ca47c740e0da05d7837ece1786bdaa249fd19a965d0
MD5 72952bca17769ba5e044e3abad4f0ae4
BLAKE2b-256 8da8e5855e7a364b38e3505f64df356a4524db8ce47a102c411ae02e9d0be1ca

See more details on using hashes here.

File details

Details for the file openimis_be_opensearch_reports-1.1.1-py3-none-any.whl.

File metadata

File hashes

Hashes for openimis_be_opensearch_reports-1.1.1-py3-none-any.whl
Algorithm Hash digest
SHA256 2929f1a6800eb6986ed72e535c716ba873937a5bb9669659ef3d3363ac900c87
MD5 6d0a0012e4c391d621183e4ad7771bd9
BLAKE2b-256 dfce356aa2169bf9029b0d1afb3c1c221aeab8e7aa3e1a13a765fa511c589907

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page