{"id":7144,"date":"2026-06-09T12:25:01","date_gmt":"2026-06-09T10:25:01","guid":{"rendered":"https:\/\/cys.group\/?post_type=article&p=7144"},"modified":"2026-06-18T14:16:28","modified_gmt":"2026-06-18T12:16:28","slug":"portal-monitor","status":"publish","type":"article","link":"https:\/\/cys.group\/en\/article\/portal-monitor\/","title":{"rendered":"Never miss a silent failure again: Introducing CYS Portal Monitor"},"content":{"rendered":"

What is Portal Monitor?<\/h4>\n

Portal Monitor is a new capability available under the Management section of the CYS portal. It brings centralised monitoring, configurable alerts, and automated notifications together in one place \u2014 giving administrators the visibility they need to stay ahead of process failures rather than react to them.<\/p>\n

With Portal Monitor, you no longer need to manually check whether your imports are running, your schedulers are firing, or your mapping processes are producing results. You define what matters, set the conditions that should trigger attention, and let the system tell you when something needs to be looked at.<\/p>\n

<\/h4>\n

What you can monitor<\/h4>\n

Portal Monitor covers four key areas of automated processing:<\/p>\n

1. Import Source Monitoring<\/strong><\/p>\n

Track import activity across all your sources, including records processed, success and failure counts, batch information, and overall runtime. If an import stops producing records or starts throwing exceptions, you will know before it becomes a problem.<\/p>\n

2. File Source Monitoring (SFTP Connectors)<\/strong><\/p>\n

Monitor when connector processes run and whether incoming files are being detected. Track file volumes, record counts within files, runtime information, and connector execution details \u2014 so you always know whether expected data is arriving.<\/p>\n

3. Project Mapping Monitoring<\/strong><\/p>\n

Gain visibility into how source data is being mapped into your project databases. Track processing outcomes across mapping runs and detect mapping exceptions or failures early, before they affect downstream data quality.<\/p>\n

4. Scheduler Monitoring<\/strong><\/p>\n

Monitor survey scheduler activity end to end \u2014 including invitations sent, reminders sent, excluded recipients, and blacklisted contacts. If a scheduler hasn’t fired or is sending fewer invites than expected, Portal Monitor gives you the signal to investigate.<\/p>\n

<\/h4>\n

Configurable alerts built around your operations<\/h4>\n

Portal Monitor does not apply a one-size-fits-all approach to alerting. You configure alerts based on your own operational thresholds and the specific processes that matter most to your organisation.<\/p>\n

For each monitored area, you can choose between a default trigger \u2014 which fires on exceptions and inactivity within the last 24 hours \u2014 or a custom trigger that gives you precise control over conditions such as:<\/p>\n

    \n
  • No records processed within a defined number of days<\/li>\n
  • Record counts that fall outside an expected range<\/li>\n
  • A scheduler that has not run within a set timeframe<\/li>\n
  • Invitation or reminder volumes that fall above or below configured thresholds<\/li>\n
  • Exception counts that exceed a defined limit<\/li>\n<\/ul>\n

    Alerts can be given a name, a start date, and an optional end date, and can be toggled on or off at any time. Each alert also includes a configurable notification message \u2014 subject line and body \u2014 so that the people receiving the notification have the context they need to act immediately.<\/p>\n

    <\/h4>\n

    Getting started in four steps<\/h4>\n

    Setting up Portal Monitor is straightforward. Navigate to Portal Monitor under Management and follow these steps:<\/p>\n

    Step 1 \u2014 Identify your critical processes.<\/strong> Decide which imports, connectors, schedulers, or mappings are business-critical and should be monitored first.<\/p>\n

    Step 2 \u2014 Configure your alerts.<\/strong> Create alerts for the scenarios that would require operational attention \u2014 imports not running, scheduler inactivity, mapping failures, or unexpected processing behaviour.<\/p>\n

    Step 3 \u2014 Set up notifications.<\/strong> Assign recipients for each alert. Notifications can be delivered as in-portal notifications to named portal users, email alerts to portal user addresses, or emails to external recipients outside the platform.<\/p>\n

    Step 4 \u2014 Monitor from the overview.<\/strong> Use the Portal Monitor overview to review recent alerts, recent process activity, triggered notifications, and operational trends across your configured processes.<\/p>\n

    <\/h4>\n

    Notifications that reach the right people<\/h4>\n

    Each alert can be configured with one or more recipients, and recipient types can be mixed within the same alert. A critical import failure, for example, could notify a portal administrator via in-portal notification and simultaneously send an email to an external operations team.<\/p>\n

    Notification messages are fully editable \u2014 the subject and body can be tailored to each alert so recipients immediately understand what has been detected and where to look.<\/p>\n

    <\/h4>\n

    The first step toward full operational visibility<\/h4>\n

    Portal Monitor is available now through the Management section of the portal. No changes to your existing processes are required to begin monitoring \u2014 simply configure your alerts and start gaining visibility.<\/p>\n

    This release represents the first step toward centralised operational visibility within the CYS platform. As more processes become monitorable and alerting capabilities expand, Portal Monitor will grow into the single place where administrators can be confident that everything critical is running as it should.<\/p>\n

    Because in research operations, the failures you never see are often the ones that matter most.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Every platform has processes that run in the background \u2014 data imports pulling in the latest records, SFTP connectors detecting incoming files, mapping rules pushing data into project databases, schedulers sending out survey invitations. These processes are often the backbone of how research operations run day to day.<\/p>\n

    But what happens when they stop working?<\/p>\n

    In most cases, no one knows right away. A scheduler that hasn’t fired in two days. An import that’s been throwing exceptions since Tuesday. A mapping process that ran but processed zero records. These failures happen silently, and by the time someone notices, the impact has already rippled through \u2014 missing data, delayed invites, unreliable reports.<\/p>\n

    Portal Monitor is our answer to that problem.<\/p>\n","protected":false},"author":13,"featured_media":7173,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false},"class_list":["post-7144","article","type-article","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/article\/7144","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/article"}],"about":[{"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/types\/article"}],"author":[{"embeddable":true,"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/users\/13"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/media\/7173"}],"wp:attachment":[{"href":"https:\/\/cys.group\/en\/wp-json\/wp\/v2\/media?parent=7144"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}