Component Diagram
The diagram below depicts DPOD's components and their interactions.
(Note: DPOD was designed for deployment using either a standalone (All in one) or distributed topology. When distributed topology is used, some of the components above will reside on different virtual/physical servers.)
...
DPOD’s sampling agents use DataPowerGateway's SOMA (SOAP configuration Management) interface for retrieving operational data for both devices (e.g. CPU, memory, load, file system and sensors) and services (e.g. service memory, service configuration). Sampling records are stored in the Big Data store.
The sampling interval used may be configured. The default sampling interval is 30 seconds for device data and 300 seconds for service data and can be changed.
WS-Management Agents (WS-M)
...
Payload recording is switched off by default, and has to be enabled manually through DPOD's user interface. For security reasons, enabling the WS-M Agents in IDG Gateway is a manual process as well. Once this is done, a subscription is registered in the WS-M agent on the monitored device.
...
The system is installed with a number of built-in reports (e.g. Services Services Elapsed Time, System Errors and Service Memory), and privileged users are able to configure new custom reports via DPOD’s Web Console.
...
Gateway Maintenance Activities
A maintenance activity defines the set of maintenance actions required for a specific goal. An example of such an activity is "Perform Secure Backup on device X".
Additionally, the maintenance activity contains other specific definitions for the action. This may include for instance which certificate should be used for the Secure Backup or which deployment policy should be used for a configuration sync operation.
Current provided activities are: backup and configuration sync.
DPOD allows users to define a plan that includes a set of target gateways on which activity will be performed and a receipt on how to perform the activities.
These Activities can be integrated into an organisation wide DevOps process by REST invocation.
Alerts
DPOD can publish alerts when certain predefined events occur, for example, when device CPU is over 80%. Alerts can be viewed and managed from the Alerts Setup page.
...
Alert Query - the metadata that defines the alert parameters (for example, count all the system errors occured occurred in the last 10 minutes in domain DMZ). There are several builtin built-in queries. Users customized threshold is a pramater parameter in the query.
Alert Execution - one execution of the alert query
...
Transactions Event Feeder
This component handle the creation and publishing of a single aggrgated logical aggregated logical transaction record.
One of the common usage is to push flat transactional data to external system or centralized data to have a flexiable and flexible and easy acces access with analytics tools.
DevOps Services Portal
DPOD now provides a new self-service DevOps portalServices Portal for traditional services. This is a new portal dashboard where end-users can:
...
Each action may be extended or customized using Python scripts. Example scripts are open source and may be obtained from a git repository - see docs documentation.
Task Scheduling Mechanism
The task scheduling mechanism consists of a scheduler and several workers.
In order to have a scalable and resilient execution of tasks, the scheduler assigns tasks to multiple workers.