Cogynt v2.14 Release Notes

Cogility is delighted to announce that Cogynt version 2.14 is generally available for AWS customers as of July 2024. Please see what’s new below.

For more information, or to have your Cogynt instance updated, please contact us.

Data Management Tool

S3 Connectors Support GeoJSONs and Arrays

Connectors now support GeoJSON and Array datatype fields within source files residing in S3 and perform the appropriate data validation.

Authoring Tool

New Projects Screen

Users can now easily view and access all projects and deployments on a single screen. This greatly simplifies managing projects and monitoring deployments.

Array-Based Partitioning

  • Users can now create partitions based on array values (or an entire array) to synthesize data streams in new ways. This is especially helpful for entity enumeration.

  • Partitioned values can now be conveniently mapped from a partition operator within computations, or to a function/operator or an output field.

New Navigation

  • Users may now switch Cogynt apps using a new app switcher, making it easier to navigate Cogynt’s offerings.

  • The new project navigation bar provides access to all tools within the a project.

  • The left sliding menu panel has been removed in favor of a more streamlined user flow.

New Error Topic

  • Users may now create models that leverage a new “error topic.”

  • When source data contains objects that do not match an expected schema, Cogynt pushes them to an error topic, where they may used in a separate pattern or used to troubleshoot.

Improved Multi-User Experience

Users are no longer locked out of patterns or computation views when another user is viewing or editing, making it easier to collaborate.

New IP Constraints

Now supporting overlaps and in Subnet constraints between two IP values.

Improved TTL Performance

TTL is now more resistant to data skew.

Enhanced Boolean Operators

The AND and OR operators now support operations over an array of Booleans.


Cogynt now supports Flink’s native Operator for Kubernetes, which enhances Cogility’s ability to support Flink’s latest features.

Resource Allocation Optimizations in Kubernetes Clusters

The production cluster now has improved resource allocation and availability. This enhancement achieves more efficient resource utilization by adjusting resource affinities and implementing priority classes. The Kubernetes cluster attains higher availability by using topology spread constraints to distribute pods evenly across all available nodes and employing pod disruption budgets to ensure that only a limited number of pods are down at any given time. As a result, the production Kubernetes cluster uses fewer nodes and maintains higher uptimes.


By deploying Redis using the bitnami/redis-cluster Helm chart on Kubernetes, production has robust and stable Redis infrastructure that scales and remains highly available. This setup minimizes operational overhead and maximizes reliability and stability, while supporting critical applications with consistent performance and uptime.


Workstation Redesign

New Navigation Bar

  • A new profile interface has been added to the user menu in the navigation bar,

  • Users may now log out of Cogynt via the user menu in the navigation bar,

  • The Admin and Designer pages have been moved to a new Settings page that can be accessed via the gear icon in the navigation bar.

  • The system notification bell icon has been moved to the navigation bar.

  • The My User Settings interface has been moved into the System Notifications drawer. This can be accessed by opening System Notifications and selecting the bell and gear icon.

Data Ingestion Screen

  • The management of data ingestion is now in a dedicated Data Ingestion page in Settings.

  • The UI for data ingestion has been redesigned to use a new table component.

  • Ingestion is now started or stopped via the Options button per row.

Event Notifications (Notification Settings)

  • The management of notification settings is now split from Data Ingestion on a new dedicated Event Notifications page in Settings.

  • The UI for Notification Settings has been redesigned to use a new table component.

Event Detail Templates

The UI for managing event detail templates has been redesigned to use a new table component.


“Views” have been renamed, and are now called “Workspaces.”

Workspaces (Formerly “Views”)

  • The tabs on the navigation bar for any open workspace now have a menu that can be accessed to perform the following actions:

    • Edit: Rename the workspace.
    • Save as Template: Save the workspace as a template.
    • Close Tab: Closes the current workspace.
  • The Auto-fit widgets button has been removed.

  • The algorithm used to place widgets and track positions on a workspace has been enhanced. Widgets have a lower chance of unintentionally shuffling positions when moving between different screen resolutions.

  • Fixed a bug where comments did not visually update when the user changed the sort preference.

Collection S3 Exports

  • A collection can now be manually exported to JSON format.

  • Cogynt can now be configured to write JSON snapshots of collections to a designated set of two S3 Datalake buckets on the following triggers:

    • collections_closed: Any time a collection is updated where the Primary Tag is changed to exactly Closed.
    • collections_working: Any time a collection is updated where the Primary Tag or Additional Tags changes.

Export Builder

The Export Builder (beta) has been retired.

User Management

  • The Roles and Groups pages have been redesigned.

  • With the new redesign of Workstations navigation the following existing permissions (TBD)

  • New My Profile modal has been implemented across all of Cogynt.

  • Default role UX has been changed.

Known Issues


  • Export actions currently require write permissions.

  • Partitioning over the url datatype can cause deployments to crash.

  • Large projects sometimes cannot be deleted due to connection timeout. As a workaround, try deleting patterns within the project to reduce its size, then attempt to delete the entire project again.

  • When a project is deleted, no project deletion audit log is generated.

  • Datetime constraints between JDBC and Kafka source types will fail. As a workaround, to perform datetime lookups, convert datetime data to epoch time (an int datatype) instead.

  • Performing an export while on the computations page can cause the application to crash.

  • The in subnet and overlaps constraints print as undefined in model documentation.

Data Management Tool

  • S3 connectors currently fail to read files in JSON array format. As a workaround, convert files to newline format if possible.

  • The browser must be refreshed to update S3 connector status.

  • S3 connectors toss records when encountering null values in fields that are configured as int or float. This can be avoided by configuring the int/float fields as strings in the connector configuration, running the connector, then creating a pattern that converts the string values to int/float.


  • Deleted comments that have children are not properly displaying the child replies on a collection.

  • In some situations, after editing a widget’s name, it may be difficult to register a mouse-click when clicking the checkmark icon. A workaround to this is to press ENTER to submit your change.

  • The sort logic for ascending and descending order for the Tag option in the Notifications Explorer widget is inverted.

  • Sorting by assignee on collections does not sort users correctly.

  • In some circumstances, a retracted pattern solution on the Drilldown widget may change color between blue and gray. Retracted pattern solutions are intended to always be gray.

  • There are rare situations in which the Drilldown widget may show outdated information for an event. If this happens, a reset should be performed to force the re-ingestion of Drilldown data.

  • After performing Dev Delete in Workstation, the list of projects in the project dropdown in the Admin screen may display incorrectly until after refreshing Workstation. In some situations, a deleted project may still appear until another deployment in Authoring is performed.

Audit Viewer

The date picker for the “Date Range” in the UI does not allow you to type in “AM” or “PM” manually. This can be worked around by clicking the calendar icon to select “AM” or “PM.”


Get Started

Ready to learn more? Contact us today!
Let's Go