> For the complete documentation index, see [llms.txt](https://host2host.onibonje.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://host2host.onibonje.com/docs/34-operations-architecture.md).

# Operations Architecture

## 1. Overview

Operational model: monitoring, incident response, runbooks, DR. Complements [Monitoring and Logging](/docs/17-monitoring-and-logging.md).

***

## 2. Operations Layers

| Layer              | Tool                       | Team                   |
| ------------------ | -------------------------- | ---------------------- |
| Real-time metrics  | Grafana / Prometheus       | NOC                    |
| Logs & trace       | OpenSearch / Jaeger        | NOC                    |
| Alerts             | Alertmanager → PagerDuty   | NOC                    |
| Transaction search | Admin ops dashboard        | NOC                    |
| Config changes     | Admin publish center       | Integration supervisor |
| DR                 | Runbooks + quarterly drill | Platform ops           |

***

## 3. Alert Severity

| Severity | Examples                             | Response          |
| -------- | ------------------------------------ | ----------------- |
| P1       | Finacle down, all payments failing   | Immediate         |
| P2       | Single partner DLQ spike, SLA breach | 1 hour            |
| P3       | Cert expiring 30 days                | 24 hours          |
| P4       | Disk usage warning                   | Next business day |

***

## 4. Runbook Index

| Runbook                       | Trigger                      | Actions                                     |
| ----------------------------- | ---------------------------- | ------------------------------------------- |
| **RB-01** Finacle unavailable | `FIN_011` spike              | Circuit breaker active; notify core banking |
| **RB-02** DLQ growth          | `h2h_dlq_messages_total`     | Ops console reprocess                       |
| **RB-03** Partner file stuck  | FILE STAGED > 30 min         | Check SFTP, reprocess                       |
| **RB-04** Config rollback     | Bad publish                  | Publish center rollback                     |
| **RB-05** Cert expiry         | `h2h.security.cert.expiring` | Vault rotate                                |
| **RB-06** Region failover     | Region health fail           | DNS + Kafka DR procedure                    |
| **RB-07** Bulk retry          | Supervisor approval          | Ops bulk reprocess API                      |

***

## 5. DR Architecture

| Component    | DR strategy                            |
| ------------ | -------------------------------------- |
| Runtime pods | Multi-AZ; secondary region standby     |
| PostgreSQL   | Streaming replication, promote replica |
| Kafka        | MirrorMaker 2 / cluster linking        |
| Vault        | HA cluster, backup unseal              |
| Config       | DB replicated; Git export backup       |

**Quarterly:** Failover drill to secondary region.

***

## 6. On-Call Rotation

NOC L1 → Integration L2 → Platform L3 → Vendor (Finacle) escalation.

***

## 7. Related Documents

* [17 Monitoring and Logging](/docs/17-monitoring-and-logging.md)
* [07 Multi-Country Deployment](/docs/07-multi-country-deployment.md)
* [22 Use Cases](/docs/22-use-cases-and-solutions.md) UC-09, UC-15, UC-16


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://host2host.onibonje.com/docs/34-operations-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.