How SNA Works

SNA is deployed as a microservice within the AA's Kubernetes cluster. It receives API requests and response data from the AA's service, aggregates SLA metrics according to Sahamati's schema, and pushes aggregated JSON payloads to the Sahamati SLA endpoint every 10 minutes.

High-Level Data Flow

The data flows through the following stages:

1. AA's service sends and receives API calls to/from FIPs and FIUs.

2. The AA service captures key metadata for every request and response at each integration point (A-H)

3. It sends this information to the SNA running in its cluster.

4. SNA aggregates the required metrics (counts, response times, percentiles, statuses) for each 10-minute window.

5. SNA pushes two JSON payloads to the Sahamati SLA endpoint every 10 minutes: one for Request metrics and one for Notification metrics.

What SNA Aggregates

Category	Type	Description
Request Metrics	Counts	Total requests sent per API type, response code counts (2xx, 4xx, 5xx)
Request Metrics	Response Times	Percentiles (p50, p95, p99, p100) per API type in milliseconds
Request Metrics	Data Size	Sum of FI/fetch encrypted data packet sizes
Notification Metrics	Counts	Total notifications received per type (FI, Account Link, Consent)
Notification Metrics	Status Breakdown	Ready, Delivered, Denied, Timeout, Pending count for FI notifications