Skip to main content
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.
  • The aso-asb app in ArgoCD syncs successfully and shows a healthy status for the production runtime. See 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.

​
Producer and consumer

  • The producer Application runs in the synchub-producer namespace and its pods are healthy. See 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.
  • 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.

​
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.
  • Each connector’s asb.event.* properties and asb.producer.apiUri property point at the production topics and producer service. See 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.
  • Sync Hub dashboards or equivalent panels are available for the production environment. See Dashboards.
  • You know how to check dead letter queues, and dead letter counts are zero after your pre-production tests. See Health and metrics.
  • Alerting covers producer and consumer errors and dead letter growth, routed to your operations team.

​
Support

​
Next steps