Primeur Online Docs
Data Watcher 1.20
Data Watcher 1.20
  • 🚀GETTING STARTED
    • What is Primeur Data Watcher
    • Main features of Primeur Data Watcher
    • Navigate through Primeur Data Watcher
  • 🔶MODEL
    • Modeling Dataflows
    • Dataflow Model lifecycle 🚀
    • Dataflow Modeler 🚀
      • Dataflow Modeler toolbar
      • Dataflow Properties panel
      • Node Properties panel
      • Matching Criteria
      • Cut-offs 🚀
      • Notifications 🚀
      • Dataflow Model attributes
  • 🕒MONITOR
    • Dataflow Inquiry 🚀
      • Dataflow Inquiry options 🚀
      • Levels of detail of the dataflow 🚀
    • Dataflow Instance attributes
    • Cut-off Board 🚀
  • DESIGN
    • Configure Dataflow attributes
    • Save and share queries
  • 🧐TROUBLESHOOTING
    • Data Watcher users 🚀
    • Data Watcher Engine extended downtime vs missing events and/or dataflows
    • How to run searches in Data Watcher
    • Data Watcher MongoDB scripts
      • Back up the Data Watcher MongoDB 🚀
      • Restore the Data Watcher MongoDB 🚀
      • Clean up the Data Watcher MongoDB
Powered by GitBook
On this page
  1. TROUBLESHOOTING

Data Watcher Engine extended downtime vs missing events and/or dataflows

When the Data Watcher Engine experiences a prolonged downtime of more than 12 hours, for whatever reason, pending unprocessed events queued up for processing on the CEMAN Broker will expire and will be automatically deleted.

These missing events will cause a faulty rendering and management of selected dataflows and/or whole dataflows not to be rendered nor managed by Data Watcher.

Additionally, when some of the dataflows involved in the outage have models with cut-offs, firing of cut-offs false alarms are expected.

PreviousData Watcher users 🚀NextHow to run searches in Data Watcher
🧐