...
(Note: DPOD was designed for deployment using either a standalone (All in one) or a distributed topology. When distributed topology is used, some of the components above will reside on different virtual/physical servers.)
...
The log collection agents receive syslog Syslog log records from the monitored devices' syslog Syslog log target, which is configured by DPOD during initial system configuration. The agents then parse the log entries, store them in the Big Data store and send them to the stream analyzing component.
...
Each monitored device's log target can send logs to a single log collection agent. However, a single log collection agent may subscribe to syslog Syslog targets originating from multiple domains on a single device or several domains on different devices.
Using DPOD's user interface, a DPOD system administrator may tune the links between syslog Syslog targets and specific log collection agent (based on the syslog Syslog target's logging rate). Doing so helps balance the network transmissions across the system and enhance throughput and log processing on DPOD's side.
During DPOD's installation process, the installer gathers environment planning and sizing request data. Based on this information, the installer creates and configures a number of log collection agents.
...
The sampling interval used may be configured. Default The default sampling interval is 30 seconds for device data and 300 seconds for service data and can be changed.
...
Once a payload is recorded by a monitored device's WS-M agent from a WS-Proxy policy, the data is then pushed to DPOD’s WS-M agent, which stores it in the Big Data store.
Payload recording puts the system under substantial load and therefore has to be manually enabled and its subscription duration is limited to 60 minutes.
Stream Processing
DPOD user uses the Stream Processing component to stream, parse and analyze incoming data. It collects data from the log collection and WS-M agents, and operates automatically without requiring maintenance.
...
The console enables the user to troubleshoot, analyze and gain insights into transaction activity on monitored devices. Privileged users may also use it to update the system configuration.
Reports
DPOD 's allows users to generate various reports through the system. These reports may be run on an ad-hoc or scheduled basis. The Reports component is responsible for processing and generating these user reports.
The system is installed with a number of built-in reports (e.g. Services Elapsed Time, System Errors and Service Memory), and privileged users are able to configure new custom reports , via via DPOD’s Web Console.
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.
...
DPOD creates a service wiki on the fly, according to configuration changes and activity data which it collects. The process creates new wiki entries for newly created services, and updates existing entries when existing services are changed. Some data Data in the wiki comes may be sourced from DataPower configuration, some from activity logs , and the rest is entered by the useror the user themselves. Both WS-Proxy (.WSP) and Multi-Protocol Gateway (.MPGW) services are documented in the wiki. See Update Wiki service JSON for more information.
...