The features listed below were added to DPOD. The following conventions are used in this document:
...
- New API Connect Recent Activity dashboard that displays a high-level overview of APIs activity.
- The Early Failing Requests Dashboard in now also available in API Connect view.
- Alerts can be generated based on some of APIs latency data.
- Auto Setup Domains feature detects a Domain Reset to auto-setup it again.
...
Users can now save favorite filter combinations and use them in subsequent sessions.
- A new free text search field was added to the Transactions List page and Raw Messages Page where the user may enter a single value that will be searched across various data fields.
- Service filter now supports auto completion.
- All applicable filters support multi-select of values.
- Users can now change the size of the series (number of values) that is displayed in charts of type "top N".
- A recent notifications panel was added to The Navigation Bar. It displays the recent UI notifications for the user (not persisted).
- A new "Share" button added. It allows sharing the current page (including filters, transaction ID etc.) by copying/pasting the current URL or by sending it via email
- Time range filters now provides more options: last 10 minutes, start of day, start of week, this month.
- Consistent behavior across pages of zoom into a transaction or use its value as a filter criteria.
...
- From time to time, DPOD customers may be required to install a new DPOD installation while preserving the data already collected. for example:
- Customer deployed DPOD Appliance mode at version v1.0.0 with CentOS 6.7 and now requires to migrate to CentOS 7.2 introduced at version v1.0.2+.
- Customer deployed DPOD on a virtual server but load increased and now requires a physical server.
- Customer deployed DPOD Appliance mode but wants to migrate to Non-Appliance mode (RHEL) to better comply with their organization security requirements and standards.
- New procedure and tools were introduced to support customers with migration of an existing DPOD Store data to a new DPOD installation in each of the scenarios above.
New Features 1.0.5
API Connect Integration
...
Display a dedicated transaction list with only API-C transactions
Filter by API-C fields (e.g. API name, API version, catalog, HTTP method, API urls and a dozen more fields)
Calculate and display latency graphs for each policy execution inside an API (including custom policies)
Provide both API-C and DataPower views of the same transaction, and the ability to switch between them
A new dashboard of APIs and the date they were last executed in the system.
API payloads may now be captured
Automatically run setup DPOD log targets for each new API-C domain created. (This requires enablement in the monitored device configuration). Further configuration based on domain name prefix is available.
To activate API-C integration, perform (from the Web Console) a re-configuration of all your log targets in the DataPower that runs the API-C domain. You can also use the auto-setup feature to handle API-C domains created in the future.
...
To activate Side Call Analysis on DPOD run re-configuration of all your log targets in the DataPower that runs the API-C domain.
...