FAQ & Troubleshooting

Q: Does SNA send any raw API request or response data to Sahamati?

No. SNA sends only aggregated metric counts and percentile values. No FI payload data, consent data, customer PII, or raw request/response bodies are ever transmitted to Sahamati.

---

Q: What if my AA serves multiple FIPs? Does SNA handle that?

Yes. The JSON payload supports a "fips" array where you can include metrics for each FIP separately. SNA aggregates per-FIP metrics automatically once the integration points are instrumented.

---

Q: How do we handle the case where no transaction was done with a particular FIP?

SNA reports only for FIPs for which it has received data. If an FIP has zero interactions in a 10-minute window, it will be omitted from that window's payload.

---

Q: What happens if SNA is down or cannot reach the Sahamati endpoint?

SNA includes retry logic for endpoint failures. Metrics that could not be pushed will be retried. If SNA itself is down, metrics for that window will be lost. Ensure that SNA has a health check configured in your cluster's liveness/readiness probes.

---

Q: Do we need to make code changes to our AA service when Sahamati updates the SLA schema?

No. Schema updates and logic changes are packaged inside new SNA versions. You only need to redeploy the updated Helm chart. Your AA service code does not need to change.

In very rare cases, if there is a change that warrants an snalib upgrade, you (AA) will have to recompile your code. If there is a change in the signature of the snalib method, you may have to make a corresponding change in your code.

---

Q: How do we know if our integration is working correctly?

You can validate your integration in UAT by monitoring the SNA logs in your cluster for push success/failure status and checking the response from the Sahamati SLA endpoint.

---

Q: What languages does snalib support?

Currently, Go, Node and Java libraries are available. Additional language support may be planned based on ecosystem demand.

---

Q: How are the synchronous transactions and asynchronous notifications correlated?

Synchronous operations: API Request and API Response - They are correlated using a "transaction correlation id" (txnCorId). This is a uuid that the AA will have to generate for every RequestIn and RequestOut, when sending to SNA. This same correlation id will have to be included when sending the corresponding ResponseOut and ResponseIn to SNA.