9.3

Edit

Application Platform Monitor

This document describes WorkFusion Platform Monitor and its features.

Features

Platform Monitor functions:

  • Monitor and troubleshoot the issues of WorkFusion components.
  • Manage RPA services.
  • Maintain active RDP session.

Main options

  • Environment Status: health status page with automated incident management.
    • Components Statuses and Health Checks: check system component health and important information about the components versions and licensees.
    • Incidents: Check current incidents timeline.
    • Email Notifications of Incidents: get the notifications about incidents and it's resolution to your email.
  • Latest Data: check the details of the components monitoring.
  • Monitoring.
    • Alerting and Notifications: check specific metrics in time like CPU or HDD usage, availability of the components by the system.
  • Proactive monitoring: forecast the system resources usage (requires separate configuration for usage).
  • Metrics collection and storage.
  • Command board: manage the components (adhoc and scheduled).
  • Bot management:
    • Process management: manage your RPA Processes.
    • Control Panel (Bot management): manage and monitor your RPAs.

Terminology

  • Platform Monitor
    This is an application which collects, aggregates and processes information about WorkFusion components. PM Agents are installed on all WorkFusion servers for gathering required metrics.
    Typically there is a main Platform Monitor instance which is responsible for aggregation of metrics from all servers, central management using web interface and heavy processing tasks (proactive monitoring):

    • PM Server: Name of server were central Platform Monitor application is installed.

    • PM Agent: an application which is installed on the servers of WorkFusion ecosystem which collects metrics from the particular components and sends to a central Platform Monitor.

  • Component Group: all components are logically subdivided into groups. Examples of groups: Control Tower, WorkSpace, OCR, RPA, Databases, Machine Learning (VDS). These groups hold number of smaller services.
  • Component: part of a service stack. Can be a single or multiple system processes, third-party service or WorkFusion applications.
  • Incident: representation of what is happening at the moment when component is not in healthy state.
  • Alert: internal object which is created when metric's value corresponds to preconfigured triggers (ex. “Response time” is large than 10 seconds). It is use to change components status and trigger arbitrary commands.
  • Health Check: a periodic check of the WorkFusion components via API and shown on the Components page.
  • Check: a periodic action that connects to some datasource and evaluates retrieved data. Each check usually generates a set of metrics
  • Metric: the measurement of a component's characteristic. Metrics can be retrieved via API in JSON format. When MongoDB is installed it is saved for plotting graphs.
  • Data source: defines some source you can use to retreive metrics or status with checks.
  • Credential: user-password pairs to be used in checks.
  • Command: arbitrary (but pre-configured) action which can be executed via API or UI to manage WorkFusion components. All command results are saved in history for tracking purposes.
  • Process: managed RPA (Bot) process which is started by WorkFusion Agent and tracked for status (automatically restarted upon failure). Process lifecycle can be managed vi API or UI. When primary process is restarted, all child processes are terminated, too.
  • Notification (email): email notification of the Incidents via SMTP protocol.
  • Bot: a single RPA entity able to execute Bot Tasks.
  • Bot Relay: the local bot controller on the RPA Server instance where the Bots are deployed.

Dependencies

Platform Monitor consists of the following components:

  • Platform Monitor application (JAR file)
  • JRE 8 runtime
  • MongoDB (optional) 3.x. It is required for the Platform Monitor to display the metrics history.

Metrics collection

Remote: Platform Monitor is collecting metrics using HTTP, SQL, MongoDB interfaces from components located on a remote server.

Local: Platform Monitor is installed on each server and can collect metrics using the command interface.

← PreviousNext →