Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Speed up your troubleshooting process by an order of magnitude, thus freeing your administrators, operators, and developers to focus on other tasks.
  • Proactive management of your DataPower Gateway network. You can quickly gain insights into services that require performance tuning (whether on DataPower or at the back-end), appliances that require upgrades in the near future, etc. and use internal builtin built-in alerts.
  • Administrators experience a noticeable reduction in support calls from consumers, developers, operators and managers. Developers and operators will be able to gain a self-service, direct, immediate insights into the workings of consumed services, and will no longer depend on the availability of a DataPower administrator for debugging and troubleshooting.
  • Managers gain a bird's-eye view of their DataPower and SOA network, supporting informed decision making and long-term planning.
  • DPOD lets you troubleshoot scenarios that current monitoring systems can not trace. E.g. A failure before a transaction started and locating a failing transaction across multiple machines and log-extensive files.
  • Run maintenance task such Configuration Sync, Device backup and firmware upgrade based on best practices scenario and across your Gateways cluster.
  • Provide internal information on execution flow, errors and latency issue for API Connect developers and admins with a unique integration with API Connect.
  • DPOD expose all traditional services in a DevOps Portal allowing users not only see and search configuration based on security role but also run such action such Service WSDL refresh.
  • DPOD produces a significant ROI shortly after deployment.
  • Additionally, DPOD improves SLA performance due to a quicker, seamless troubleshooting process.

...

DPOD leverages existing Datapower Gateway capabilities to perform its data collection.

...

  • Raw DataPower logs – Including all information issued by DataPower processes, as well as sysouts from custom DataPower integration code.
  • Device-level data - Hardware, CPU, memory, etc. as well as configuration information such as domains, services, and more.
  • Service-level data - Memory consumption, configuration data, errors to success ratios, etc.
  • Transaction performance and latency information - This includes front-end and back-end latency, as well as detailed memory consumption analytics for each action within a particular DataPower policy.
  • Security data – Including certificate expiration, content violations, encryption errors, and more.
  • Payload data - Available on an ad-hoc basis, only when enabled via WS-M.
  • Configuration Data - Service configuration is collected and prepared for search and run, impact analysis. Configuration is also expose in a DevOPs Portal.
  • Audit logs - Including restarts time and firmware level changes over time.

 

...