Skip to content

18 April 2023 Release Notes

Application version 1.0; User interface version 1.20.4

Feature highlights

New component types!

Observability now supports four component types: batch pipelines, datasets, streaming pipelines, and servers.

The uniqueness of each component means that the tools and assets in your data estate can be more accurately represented when you build journeys and investigate instances.

To learn more, see our help documentation on Components.

Other fixes and enhancements

  • We've made improvements to our navigation:
    • On the Overview page, investigate historical journey data, then jump back to today. Click Today to return to the current day's instances from any moment in the past. [PD-1256]
    • Move through an instance's batch pipeline run results with a single click. From the Status tab, click the <x> runs link of any batch pipeline component to go to the Batch Runs tab. Here, the runs in the list will be automatically filtered for that batch pipeline. For more information, see Instance Details Status Tab. [PD-1268]
  • The key that identifies a component no longer needs to be unique within a project. If a key is repeated, the system is able to identify the correct component based on the unique combination of the component type and key value. Keys used within a type of component still need to be unique. [PD-1211]
  • For users that work in both DataOps Automation and DataOps Observability:

The DataOps Automation Python package, DKUtils, has had its Events Ingestion Client dependency locked to version 1.0. This is to avoid potential compatibility issues during the development and release of the Events Ingestion Client version 2.0. [PD-1210] - We applied general fixes to reduce errors. - We made various improvements to our user experience. Our help documentation has been updated to reflect these changes.