Skip to main content
Version: 2.11.X

Cogynt v2.11 Release Notes

Cogility is delighted to announce that Cogynt version 2.11 is generally available for both AWS and GCP customers as of October 2023. Please see what's new below.

If you'd like more information, or want to have your Cogynt instance updated, please contact us.

Authoring Tool

User Experience Improvements

  • The character limit for project and deployment names has been increased to 50 characters.

  • A default deployment target is created upon project creation.

    • Event types are no longer created without a datasource reference.
    • There is always a default deployment target to select from when creating a deployment.
  • Added a time unit dropdown menu for Flink timeout configuration settings.

  • The deployment loading screen has been removed in favor of a simple status indicator when a deployment is still initializing. The new status is Initializing. This allows the user to deploy another job immediately without having to wait for a loading screen to free up the UI.

  • Custom deployment configurations now auto-detect the value datatype to be submitted upon deployment.

  • The Flink dashboard can now be accessed via a new dashboard icon on each deployment object in the deployment table.

  • The URL to the Flink dashboard is no longer displayed on the UI.

  • The URL is now a hash ID of the deployment instead of an amalgam of the project and deployment name.

  • The deployment hash-ID, labeled "Flink Cluster Name", can be copied with a quick copy icon provided in the expanded view of the deployment. This ID can be used as a reference key for advanced debugging in the Kubernetes dashboard.

Performance Improvements and Refactoring

  • Backend and frontend improvements have increased Cogynt's speed and usage efficiency of infrastructure resources.

  • Improved Flink checkpointing efficiency.

  • Improved countUnique function performance.


Observability Improvements

  • Administrators are now able to view several dashboards within Grafana.

  • These dashboards allow admins to monitor system performance and respond to possible issues.


Custom Fields

  • Added the ability for users to create "Groups" to organize custom field templates.


  • The "Custom Fields" mode of a collection now hides custom fields within groups that are expandable or collapsible to improve the mode's visual layout.

  • Enhanced hover for collection cards:

    • Hovering over the Primary User icon now also displays participants.
    • Hovering over the Primary Tag color now displays the full name of the tag.
    • Added a new icon to collections to represent the primary and additional tags assigned to a collection.
  • Improved the querying experience by adding a glyph that shows how many connections a node has, making it more obvious that there are more connections that can be queried.

  • Adjusted the query depths on the Link Analysis drop zones to better reflect the new querying experience. Level 1 plots only the node that the user has placed.

  • Double-clicking a node now queries an additional two levels of connections.

  • Added risk glyphs to the Link Analysis nodes.

  • Added Social Network Analysis.


  • The Drilldown chart now defaults to showing summary nodes instead of the entire chart. Users can double-click any node in the graph to expand the next level of the tree. Expand All and Collapse All are added to the context menu upon right-clicking the background.

  • The appearance of a Drilldown event sent to the Object Details Viewer now has been restyled to look more similar to a normal event.

Map Widget

  • Fixed a bug introduced in Map widget in Cogynt 2.10.X where the globe view of the map widget did not render in the appropriate size.

Event Details Viewer

  • A Drilldown tab has been added so that users can view Drilldown chart for an event (if applicable) without needing a dedicated Drilldown widget.

Report Builder

  • Added the ability to import and export a Report Builder template.

  • The Create and Open interfaces for Report Builder templates have been redesigned.

  • Comments with tagged users now show the user name instead of user ID on any exported reports.

UX Improvements

  • Added automatic scrolling when an item is being dragged to the upper or lower part of a screen.

  • Implemented right-click actions for appropriate objects with the ability to Send to Object Details Viewer, Open in new viewer widget, and Send to another View.

  • Objects with right-click actions are found on:

    • Events: On the Events Stream widget (right-click the drag icon) or linked to Collections.
    • Collections: On the Collections widget or linked to Events.
    • Notifications: On the Notifications and Notifications Explorer widgets.

User Management

  • The Workstation permissions for Export and Report Builder have changed to control only who can modify an export or Report Builder template.

  • A user that has "Collection Export" permissions can now export a collection without having "Export" and "Report Builder" permissions.

Known Issues

Data Management Tool

  • Failed upload attempts are not logged in audit logs.

  • Using an S3 connector to read tab separated files results in null events. Avoid using tab separated files with the S3 connector.



  • Project modified time is updated upon entering and viewing the project despite no changes being made.

  • Windowing results miss events if the source topic has more than a single partition. To avoid this issue, the source topic must be configured with one a single partition.

  • Flink jobs crash if attempting to access a nest field that does not exist.

  • Exporting cloned patterns sometimes also exports the original parent of the copy alongside the new pattern.

  • Resuming a paused deployment sometimes fails to start from the savepoint, and instead deploys from the beginning if the pod restarts upon deployment.

  • The partition count remains 0 even when a pattern is partitioned over a window.

  • If a pattern is created that has an issue (for example, if no constraints are given between source events), and then that pattern is deleted using the top-right Delete option, the system does not clear those issues automatically. If those old issues are clicked, Authoring crashes, pointing to a pattern that no longer exists. (If another action is taken instead, like creating a new pattern, the issues are cleared.)


  • The GeoContains function returns null.

  • The Avg function for a set of arrays returns a single float rather than the expected set of floats (a resulting average value for each array in the set).

  • The product function produces null outcomes when the product operates between sets and scalar values.

  • The greater than and less than comparison operations produce nulls for operations between sets and scalar.

  • FirstNonNull operations produce null results for operations between set and scalars.

  • toIP returns invalid / inaccurate results instead of nulls when invalid data is received.


  • Turning off the Title column in the Events Stream widget crashes the view. Refresh your browser tab to restore the view.

  • 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, perform a reset 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.

Did you find the information that you needed?