.. _manager_monitor:

Online Monitor
####################

.. toctree::
   :maxdepth: 1

.. contents::
   :local:

.. role:: ex

.. role:: code

.. _manager_online_monitor:

Overview
==============

| The screen is located in “Tools” – “Monitoring” section. This screen displays information about various errors that usually require quick response, as well as the options to subscribe for notifications about any errors via Telegram, Email or Push notification. Phone number and e-mail address are taken from the personal account (Manager or its employee account).
|

.. image:: ../../_static/images/9/tasks_mer_new.png
  :width: 800
  :align: center
  :alt: pic92 manager faq

.. _manager_perilous_decline:

Perilous Decline
============================

| This section is located in :ref:`manager_online_monitor`. This section displays triggered perilous declines which were selected by Manager.
| To create a list of perilous declines, use :ref:`Processor Error Codes screen<pressor_errors>`.
| If Perilous declines list is empty please contact with support.
|

.. image:: ../../_static/images/9/perilous_decline_new.png
  :width: 800
  :align: center
  :alt: perilous decline

.. _manager_disabled_scheduled_adjustments:

Disabled Scheduled Adjustments
==========================================

| Disabled scheduled adjustments is necessary to receive notifications when automatic adjustments are disabled due to a negative balance or merchant deactivation.
|

.. image:: ../../_static/images/9/disabled_scheduled_adjustments_new.png
  :width: 800
  :align: center
  :alt: disabled scheduled adjustments

|

Balance Running Out
===================

| This alert is used if necessary to receive notification when the Merchant Live balance is equal or under 1000$.
|

.. image:: ../../_static/images/9/balance_running_out_new.png
  :width: 800
  :align: center
  :alt: disabled scheduled adjustments

|

Important Filters
=================

Notifications can be created for cases in which transactions were filtered due to the one of the following filters:

1. :ref:`Source Credit Card Number usage frequency for Email or IP address<source_credit_card_number_usage_frequency_for_email_or_IP_address>`
2. :ref:`Source Credit Card Number approved transaction interval<source_credit_card_number_approved_transaction_interval>`
3. :ref:`Total Credit Card Number usage frequency for last 24 hours (daily limit)<total_credit_card_number_usage_frequency_for_last_24_hours_daily_limit>`

.. list-table::
   :widths: 30, 70
   :header-rows: 1
   :class: longtable

   * - Field name
     - Description
   * - Date
     - The date when alert has been created.
   * - ID
     - Alert identification number.
   * - Name
     - Name of the Merchant.
   * - MerchantID
     - Merchant identification number.
   * - Error Description
     - Triggered project filter error description with error code. Example: [1033] Too many approved transactions for the same credit card number.

|

.. image:: ../../_static/images/9/important_filters_new.png
  :width: 800
  :align: center
  :alt: disabled scheduled adjustments

|