Impulse Dev Manual
HomePricingContact Us
  • Understanding Impulse Sync
  • Understanding how Impulse diffs content
  • Understanding Job Scheduling
  • Motation
    • Content Motation
    • Definition Motation
    • Domain Motation
    • Folder Motation
    • Language Motation
    • Relationship Motation
    • Tag Motation
  • Connectors
    • Source Connector
    • Destination Connector
    • Go Code
    • IDs
    • ID Mapping
    • Testing Controller
      • Implementation
  • Motators Binary
    • Implementation
    • Go Code
  • Services
    • Connector Depot
    • Motator Binary Depot
    • Job Depot
    • Endpoint Depot
    • Sync Manager
    • Content Diffuser
    • Pickup Taxi
    • Dropoff Taxi
    • Pipeliner
    • Scheduler
    • Motator
    • Motator Service
  • Watchdog Process
    • Watchdog flow
  • Impulse License
  • Troubleshooting
    • Job Config
    • Transaction Audit Trail
  • gRPC
    • Protocol buffer compiler
  • Test Commands
  • Glossary
Powered by GitBook
On this page

Was this helpful?

Watchdog Process

As each Microservice consumes a message that was produced by the Sync Manager the Sync Manager is used to handle the Watchdog process in order to validate the health of each produced message, this Watchdog process starts a Heartbeat on each produced message and listens for Heartbeats Pulses sent by the consumers associated to these individuals produced messages in order to track the status of these processes and in case of errors be able to retry the failing message.

The Watchdog process is able to:

  1. Identify if a produced message was Delivered.

  2. Identify if the process associated with the delivered message when it is consumed is In Progress.

  3. Identify if the process associated with the delivered message when it is consumed is Done.

  4. Identify if the process associated with the delivered message when it is consumed Failed.

  5. Identify if the process associated with the delivered message when it is consumed takes too long to finish.

  6. Retry messages that were never delivered.

  7. Retry messages of idle processes, for example, messages that were delivered, but due an unexpected error the node was shutdown, when the node is back up again the retry process in the watchdog will send the message again.rawdataid

  8. Retry messages where the process associated with the delivered message when it is consumed Failed.

PreviousMotator ServiceNextWatchdog flow

Last updated 2 years ago

Was this helpful?