Overview

Portal Monitor is designed to help you gain better visibility into important portal processes and proactively identify issues before they impact your operations

What is Portal Monitor?

Many portal activities such as imports, schedulers, connectors, and mappings run in the background. When these processes stop running, fail unexpectedly, or behave differently than expected, identifying the issue can be difficult and time-consuming. Portal Monitor helps solve this by centralizing monitoring, alerting, and notifications in one place.

What Portal Monitor helps you do

With Portal Monitor, you can:

• Monitor important portal processes and activities

• Detect failures, inactivity, and exceptions earlier

• Configure alerts based on operational conditions

• Receive notifications when attention is required

• Improve visibility into automated processing

• Reduce manual troubleshooting effort

SFTP connector monitoring

Track when connector processes run and monitor:

  • File detection
  • Runtime information
  • Process details

Import Source Monitoring

Monitor import activity including:

  • Records processed
  • Success and failure counts
  • Import runtime
  • Batch information

Mapping data to Database

Identify and track mapping rule failures and processing exceptions.

Personal Invite scheduler monitoring

Monitor scheduler activity including:

  • Emails sent
  • Blacklisted recipients
  • Temporary exclusions
  • Scheduler execution details

Alerts and Notifications

Portal Monitor allows you to configure alerts based on monitored activity.

Examples include:

  • No activity detected for a configured period
  • Exceptions occurring during processing
  • Unexpected process behavior
  • Processing thresholds being exceeded

When an alert condition is met, notifications can be sent automatically.

How can you utilise the Portal Monitor?

Portal Monitor is available through the new Portal Monitor section under Management.

Step 1: Identify critical processes

Determine which imports, connectors, schedulers, or mappings are business-critical and should be monitored.

Step 2: Configure alerts

Create alerts for scenarios that require operational attention, such as:

  • Imports not running
  • Mapping failures
  • Scheduler inactivity
  • Unexpected processing behavior

Step 3: Configure notifications

Assign the appropriate recipients for notifications using portal notifications or email.

Step 4: Monitor activity

Use the Portal Monitor overview to review:

  • Recent alerts
  • Recent process activity
  • Triggered notifications
  • Operational trends

Read the following article to understand how to Create/Edit an alert