SahamatiNet
  • Background
  • SahamatiNet POC
    • Introduction
    • Applications
    • Observability
    • Integration Steps
      • Sandbox Onboarding
      • IAM APIs
      • CR APIs
      • Integration with Router
        • Sample Code Snippets
          • Python
          • Java
          • JavaScript
          • GoLang
          • C#
        • Router APIs Specifications
          • FIU API Specification
          • AA API Specification
          • FIP API Specification
      • ReBIT Workflows using Router
        • Account Discovery & Linking
        • Consent Workflow
        • FI Request Workflow
    • Integration with Simulators
      • AA Simulator
      • FIP Simulator
      • FIU Simulator
    • Validation of Integration
  • Glossary
  • Guidelines
  • Frequently Asked Questions
  • How To Guides
    • How To Onboard to Sandbox ?
    • How To Decide on an Entity ID ?
    • How To Generate a Certificate ?
    • How To Generate Tokens ?
Powered by GitBook
LogoLogo

Copyright © 2025 - Sahamati Foundation

On this page

Was this helpful?

Export as PDF
  1. SahamatiNet POC

Observability

PreviousApplicationsNextIntegration Steps

Was this helpful?

SahamatiNet Router serves as an additional layer on top of the AA network, offering extra services and policies. By integrating with the Sahamati Router, FIUs, FIPs, and AAs can seamlessly connect with all other entities within the Router. This eliminates the need for multiple integration points, significantly reducing the integration and operational efforts for members

Comprehensive Technology Infrastructure – SahamatiNet

SahamatiNet - Services on Observability

MIS :

Daily reports on Discovery, Linking, Consent, and data fetch, generated from the Router’s meta data. Will be more accurate that currently available due to varying cadences, formats, incorrect data and naming conventions.

Network Health :

Complete picture of health of FIP and AA applications derived from a single source of truth. Avoids overlapped calls from AAs to the FIPs and ecosystem health reporting is not dependent on vagaries of reporting.

SLA Reporting :

  • Report on SLA Adherence for each scenario’s success case, error rate for AAs and FIPs.

  • Need to define and agree SLAs for each ecosystem participants and report on adherence and Report on non-adherence to SLA commitments

NOC Support :

  • Sahamati NOC Support using Network Health metrics and SLA Adherence

  • Facilitates proactive action to correct ‘sick’ nodes

  • Grievance Redressal

Technical Audit :

  • API Telemetry

  • Tracking of changes in Ecosystem such as onboarding of REs, ad

Billing and Recon :

Generate data fetch statements to support downstream billing & any reconciliation efforts amongst participants bilaterally