> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Sync Hub go-live checklist

> Verify Sync Hub topics, services, connectors, and monitoring before you go live

Complete the following checks before you go live with connectors that use Sync Hub. Each item links to the documentation that explains how to verify or fix it.

## Infrastructure

* [ ] Topics and subscriptions for production exist in the `servicebus.values.yaml` file under the `synchub` folder of the production runtime, and ArgoCD applies them through Azure Service Operator. See [Topic and subscription management](/platform/sync-hub/deployment#topic-and-subscription-management).
* [ ] The `aso-asb` app in ArgoCD syncs successfully and shows a healthy status for the production runtime. See [How ArgoCD applies changes](/platform/sync-hub/deployment#how-argocd-applies-changes).
* [ ] Session configuration matches: `requiresSession` on each subscription (from the `servicebus.values.yaml` file) equals `sessionEnabled` for that subscription in the consumer configuration. See [Azure Service Bus configuration](/platform/sync-hub/deployment#azure-service-bus-configuration).

## Producer and consumer

* [ ] The producer Application runs in the `synchub-producer` namespace and its pods are healthy. See [Deploy the producer](/platform/sync-hub/deployment#deploy-the-producer).
* [ ] The `backbase.grandcentral.events.servicebus.activeTopics` property (from the producer Helm values) lists every production topic your connectors publish to. The producer fails on startup when this property is empty.
* [ ] The consumer Application runs in the `synchub-consumer` namespace and its pods are healthy. See [Deploy the consumer](/platform/sync-hub/deployment#deploy-the-consumer).
* [ ] Every topic and subscription pair that routes to a Unified API has a `topicEndpoints` entry (from the consumer Helm values) with the correct `outboundConnectorUrl`, `subscriptionkey`, and `httpMethod`. See [Azure API Management configuration](/platform/sync-hub/deployment#azure-api-management-configuration).

## Connector integration

* [ ] Each connector that publishes to Sync Hub carries the pod labels `app.gcservices.io/synchub-enabled: "true"` and `app.gcservices.io/synchub-type: "producer"` through `connector.customLabels` in its `values.yaml` file. See [Connector labels required](/platform/sync-hub/deployment#connector-labels-required).
* [ ] Each connector's `asb.event.*` properties and `asb.producer.apiUri` property point at the production topics and producer service. See [Connector properties](/platform/sync-hub/events-and-files-reference#connector-properties).
* [ ] Publish a test event per topic in a pre-production runtime and confirm it reaches the expected consumer or Azure API Management (APIM) endpoint.

## Monitoring and alerting

* [ ] You can see producer and consumer logs in Grafana for the production environment. See [Logs](/platform/sync-hub/monitoring#logs).
* [ ] Sync Hub dashboards or equivalent panels are available for the production environment. See [Dashboards](/platform/sync-hub/monitoring#dashboards).
* [ ] You know how to check dead letter queues, and dead letter counts are zero after your pre-production tests. See [Health and metrics](/platform/sync-hub/monitoring#health-and-metrics).
* [ ] Alerting covers producer and consumer errors and dead letter growth, routed to your operations team.

## Support

* [ ] Your team knows how to contact Backbase support and what details to include. See [Get help](/platform/sync-hub/monitoring#get-help).
* [ ] Your operations runbook references [Monitor and troubleshoot Sync Hub](/platform/sync-hub/monitoring) for common errors.

## Next steps

* [Sync Hub deployment and configuration](/platform/sync-hub/deployment): Fix any item that fails verification.
* [Monitor and troubleshoot Sync Hub](/platform/sync-hub/monitoring): Set up dashboards, log queries, and alerts.
* [Sync Hub overview](/platform/sync-hub/overview): Return to the Sync Hub overview.