...
...
...
...
...
...
...
...
...
...
...
Component Diagram
The diagram below depicts DPOD's components and their interactions.
...
A new DPOD installation sets up a Big Data store that is preconfigured pre-configured and optimized for DPOD's requirements. As the storage is managed automatically by DPOD’s internal components, no regular maintenance is required by users.
...
Using DPOD's user interface, a DPOD system administrator may tune the links between Syslog targets and specific log collection agent (based on the Syslog target's logging rate). Doing so helps balance the network transmissions across the system and enhance enhances throughput and log processing on DPOD's side.
...
The DPOD WS-M agents, using the WS-Management agent on monitored devices, are responsible for processing and storing the monitored devices' service payload recording from WS-Proxy services,
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 is a manual process as well. Once this is done, a subscription is registered in the WS-M agent on the monitored device.
...
Payload recording puts the system under substantial load and therefore has to be manually enabled and its maximum duration is limited up to 60 minutes.
Stream Processing
...
Reports can be saved as CSV files on the DPOD appliance file system, or sent as mail attachment via SMTP and a custom web service.
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 will include includes a set of target gateways on which activity will be perform performed and a reciept receipt on how to perform the activities.
This These Activities can be integrate in organisational wider integrated into an organisation wide DevOps process by RESR 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
...
TODO NM
Internal Alerts
TODO NM
Transactions Event Feeder
TODO NMSetup page.
An alert consists of:
Alert Query - the metadata that defines the alert parameters (for example, count all the system errors occured in the last 10 minutes in domain DMZ). There are several builtin queries. Users customized threshold is a pramater in the query.
Alert Execution - one execution of the alert query
Alert Publishing - when an alert returns (positive) results, it will be published to interested parties via email or syslog
Internal Alerts
DPOD can send alerts on its internal services and component health status.
Transactions Event Feeder
This component handle the creation and publishing of a single aggrgated 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 easy acces with analytics tools.
DevOps Services Portal
DPOD now provides a new self service DevOps portal for traditional services. This is a new portal dashboard where end-users can:
...