Skip to content

Module Map

This page maps the main modules that shape IntegraMon at runtime. It is intentionally practical: the goal is to know where a behavior lives before diving into code or changing a process.

Frontend entry points

  • frontend/src/route/Routes.jsx Central route map for dashboards, tenant views, admin, superadmin, /docs, and /sysdocs.
  • frontend/src/pages/components/config/AddConfigWizard.jsx First-time tenant creation flow and default builder.
  • frontend/src/pages/components/config/Config.jsx Main tenant workspace that loads overview, settings, alerts, messages, packages, artifacts, archives, and keystore views.
  • frontend/src/pages/components/config/ConfigOverview.jsx Operational overview entry for tenant-centered monitoring actions.
  • frontend/src/pages/components/focused/FocusedConfig.jsx Focused monitoring view for rapid inspection of alerts, messages, and artifacts.
  • frontend/src/pages/components/config/ConfigSettings.jsx Ongoing tenant maintenance after creation.

Backend configuration and access

  • backend/src/core/views.py CRUD APIs for cConfig, cConfigExt, access mappings, import/export, and supporting config services.
  • backend/src/core/models.py Tenant-level metadata such as cConfig, cConfigExt, notifications, HTML templates, cleanup history, and admin settings.
  • backend/src/core/views_admin.py Admin and superadmin backend operations including cleanup, metrics-related screens, and shared management data.

CPI domain backend

  • backend/src/cpi/views.py Read APIs and action endpoints for messages, alerts, packages, artifacts, archives, and derived tenant runtime data.
  • backend/src/cpi/models.py Domain tables for message logs, correlations, payloads, alerts, packages, flows, keystore entries, and archives.
  • backend/src/cpi/urls.py Public URL map for CPI-related frontend calls.

Worker and runtime modules

  • backend/src/cpi/worker.py Main recurring runtime loops for package sync, payload sync, message sync, alert runs, archive processing, and related tenant background work.
  • backend/src/cpi/tasks/task_alerts.py Alert scheduling and orchestration entry points.
  • backend/src/cpi/alerts_message.py Message-based alert evaluation.
  • backend/src/cpi/alerts_iflow.py Flow and package health alert evaluation.
  • backend/src/cpi/alerts_keystore.py Certificate and keystore-related alert evaluation.
  • backend/src/core/worker_logging.py Logging path resolution and worker log support driven by tenant configuration.

Documentation modules

  • backend/src/core/docs_service.py Source-aware docs indexing, tree generation, page loading, role filtering, and search.
  • backend/src/core/views_docs.py Docs API endpoints used by the shared documentation frontend.
  • frontend/src/pages/docs/DocumentationCenter.jsx Shared docs shell for both /docs and /sysdocs, including stable scrolling, TOC, search, and markdown rendering.

Module relationships

flowchart TD
    Routes[Routes.jsx] --> Wizard[AddConfigWizard.jsx]
    Routes --> Config[Config.jsx]
    Config --> Overview[ConfigOverview.jsx]
    Config --> Settings[ConfigSettings.jsx]
    Config --> DetailPopups[Alerts, Messages, Packages, Archives, Keystore]
    Wizard --> CoreViews[core/views.py]
    Settings --> CoreViews
    Overview --> CpiViews[cpi/views.py]
    DetailPopups --> CpiViews
    CoreViews --> CoreModels[core/models.py]
    CpiViews --> CpiModels[cpi/models.py]
    Worker[cpi/worker.py] --> CoreModels
    Worker --> CpiModels

Reading tip

When analyzing a feature, start from the user entry point, then the API endpoint, then the persisted model or worker logic. That route usually reveals both the business intent and the runtime side effects fastest.